android boot - where is the init.%hardware%.rc read in init.c ? where are services started?

Question

Going through the code in init.c and trying to figure out 2 things:

An example of an init.%hardware%.rc would be appreciated.

It's sometimes hard to track which of various possibilities in source end up on a runnable build. I believe recent Android releases now have a working `grep` with the -R recursive flag, so I might be tempted to use that on an emulator to figure out where these things are in that particular example. It would be harder on a device since so much is locked down now even against reading, but on the emulator the adb shell runs as root. — Chris Stratton, Dec 13 '13 at 18:01
@ChrisStratton: I am mainly interested in a general walkthrough of the boot process, not in any particular device's very precise boot details — Mr_and_Mrs_D, Dec 13 '13 at 18:12

score 4 · Accepted Answer · edited May 23 '17 at 12:17

Ok got it - both questions are answered in init.rc.

hardware specific init.%hardware%.rc read at http://androidxref.com/4.3_r2.1/xref/system/core/rootdir/init.rc#8, where we see the line
```
import /init.${ro.hardware}.rc
```
Now, ro.hardware is read from the command line (main, process_kernel_cmdline and finally export_kernel_boot_props). Where is the command line, well...
Services started: in main the boot action is triggered, which contains the lines
```
class_start core
class_start main
```
that start all the core and main services. Got the info from Where are the Android system services started?

NB: I refer to KitKat - YMMV

1 Answers1