android init

README.adoc

@@ -7668,7 +7668,7 @@ Also both can use very similar techniques: either link:lhttps://en.wikipedia.org
 
 The huge advantage of QEMU over VirtualBox is that is supports cross arch simulation, e.g. simulate an ARM guest on an x86 host.
 
-QEMU is likely the leading cross arch system simulator as of 2018. It is even the default Android simulator that developers get with Android Studio 3 to develop apps without real hardware.
+QEMU is likely the leading cross arch system simulator as of 2018. It is even the default <<android>> simulator that developers get with Android Studio 3 to develop apps without real hardware.
 
 Another advantage of QEMU over virtual box is that it doesn't have Oracle' hands all all over it, more like RedHat + ARM.
 
@@ -11648,6 +11648,27 @@ as mentioned at: https://android.stackexchange.com/questions/77280/allow-unknown
 
 Tested on: `8.1.0_r60`.
 
+=== Android init
+
+For Linux in general, see: <<init>>.
+
+The `/init` executable interprets the `/init.rc` files, which is in a custom Android init system language: https://android.googlesource.com/platform/system/core/+/ee0e63f71d90537bb0570e77aa8a699cc222cfaf/init/README.md
+
+The top of that file then sources other `.rc` files present on the root directory:
+
+....
+import /init.environ.rc
+import /init.usb.rc
+import /init.${ro.hardware}.rc
+import /vendor/etc/init/hw/init.${ro.hardware}.rc
+import /init.usb.configfs.rc
+import /init.${ro.zygote}.rc
+....
+
+TODO: how is `ro.hardware` determined? https://stackoverflow.com/questions/20572781/android-boot-where-is-the-init-hardware-rc-read-in-init-c-where-are-servic
+
+Tested on: `8.1.0_r60`.
+
 == About this repo
 
 === Supported hosts