分析Android 根文件系统启动过程(国外英语资料).doc

分析Android 根文件系统启动过程(国外英语资料) Analysis of the Android root file system startup process (init daemon analysis) Daemon, Android, file system, init, process In the Android system startup, the kernel boot parameters are set to init=/init, in this case, if the kernel successfully mounted the file system after the first operation is the root directory of the init program. What does this program do? We only have RFSC (Readthe, Fucking, Source, code)!! Init program source code, in the official Android source code system/core/init, main in init.c. Our analysis starts with main. Init: (1) install the SIGCHLD signal. If the parent process does not wait until the end of the child process, the child process will become a zombie process (zombie), which takes up system resources. Therefore, SIGCHLD signals need to be processed to recover the resources of the zombie process and avoid unnecessary waste of resources. (2) clearing umask. What is umask, please see /showArticle/53978.shtml (3) set up the necessary folders for rootfs and mount the appropriate partitions. /dev (TMPFS) /dev/pts (devpts) /dev/socket /proc (proc) /sys (sysfs) (4) create /dev/null and /dev/kmsg nodes. (5) parse /init.rc, adding all the services and operations information to the list. (6) extract information kernel startup parameters from /proc/cmdline and save them to global variables. (7) obtain the information, hardware information and version number from the global variables acquired in the previous step. If not, then extract them from /proc/cpuinfo and save them to global variables. (8) select a /init. (hardware).Rc according to the hardware information, and parse the service and operation information into the list. In the G1 ramdisk root directory, there are two /init. (hardware).Rc:init.goldfish.rc and init.trout.rc, and the init program selects an analysis based on the hardware information obtained earlier. (9) execute the command triggered by early-init in the linked list. (10) traversing the /sys fold