The init module starts system service processes from the time the kernel loads the first user-space process to the time the first application is started. In addition to loading key system processes, the module needs to configure their permissions during the startup and keep the specified process alive after sub-processes are started. If a process exits abnormally, the module needs to restart it, and to perform system reset for a special process.
init divides the system startup into three phases:
pre-init: operations required before system services are started, for example, mounting a file system, creating a folder, and modifying permissions
init: operations required for starting system services.
post-init: operations required after system services are started.
In the **init.cfg** file, each of the preceding phases is represented by a job, which corresponds to a command set. The init\_lite module initializes the system by executing the commands in each job in sequence. Jobs are executed in the following sequence: pre-init \> init \> post-init. All jobs are stored in the **jobs** array in the **init.cfg** file.
In addition to the **jobs** array, the **init.cfg** file also provides a **services** array, which is used to store the names, executable file paths, permissions, and other attribute information of the key system services that need to be started by the init process.
The file is stored in **/vendor/hisilicon/hispark\_aries/init\_configs/** under **/etc/**. It is in JSON format, and its size cannot exceed 100 KB.
The format and content of the **init.cfg** file are as follows:
<tdclass="cellrowborder"valign="top"width="86.6%"headers="mcps1.2.3.1.2 "><pid="p18115019284"><aname="p18115019284"></a><aname="p18115019284"></a>Job that is executed first. Operations (for example, creating a folder) required before the process startup are executed in this job.</p>
<tdclass="cellrowborder"valign="top"width="86.6%"headers="mcps1.2.3.1.2 "><pid="p14818016288"><aname="p14818016288"></a><aname="p14818016288"></a>Job that is executed in between. Operations (for example, service startup) are executed in this job.</p>
<tdclass="cellrowborder"valign="top"width="86.6%"headers="mcps1.2.3.1.2 "><pid="p18116016285"><aname="p18116016285"></a><aname="p18116016285"></a>Job that is finally executed. Operations (for example, mounting the device after the driver initialization) required after the process startup are executed in this job.</p>
</td>
</tr>
</tbody>
</table>
A single job can hold a maximum of 30 commands \(only **start**, **mkdir**, **chmod**, **chown**, **mount**, and **loadcfg** are supported currently\). The command name and parameters \(128 bytes or less\) must be separated by only one space.
<thclass="cellrowborder"valign="top"width="34.089999999999996%"id="mcps1.2.4.1.2"><pid="p3381142134118"><aname="p3381142134118"></a><aname="p3381142134118"></a>Format and Example</p>
<tdclass="cellrowborder"valign="top"width="55.76%"headers="mcps1.2.4.1.3 "><pid="p56817536457"><aname="p56817536457"></a><aname="p56817536457"></a>Creates a folder. <strongid="b1111653719537"><aname="b1111653719537"></a><aname="b1111653719537"></a>mkdir</strong> and the target folder must be separated by only one space.</p>
<tdclass="cellrowborder"valign="top"width="55.76%"headers="mcps1.2.4.1.3 "><pid="p2023822074614"><aname="p2023822074614"></a><aname="p2023822074614"></a>Modifies the permission, which must be in the <strongid="b8112193214139"><aname="b8112193214139"></a><aname="b8112193214139"></a>0<emid="i11455534181314"><aname="i11455534181314"></a><aname="i11455534181314"></a>xxx</em></strong> format. <strongid="b2675148175310"><aname="b2675148175310"></a><aname="b2675148175310"></a>chmod</strong>, <emid="i46798488538"><aname="i46798488538"></a><aname="i46798488538"></a>permission</em>, and <emid="i667944825318"><aname="i667944825318"></a><aname="i667944825318"></a>target</em> must be separated by only one space.</p>
<tdclass="cellrowborder"valign="top"width="55.76%"headers="mcps1.2.4.1.3 "><pid="p18408185817467"><aname="p18408185817467"></a><aname="p18408185817467"></a>Modifies the owner group. <strongid="b19641958195310"><aname="b19641958195310"></a><aname="b19641958195310"></a>chown</strong>, <strongid="b15698584534"><aname="b15698584534"></a><aname="b15698584534"></a>uid</strong>, <strongid="b1692058135310"><aname="b1692058135310"></a><aname="b1692058135310"></a>gid</strong>, and <emid="i56935885316"><aname="i56935885316"></a><aname="i56935885316"></a>target</em> must be separated by only one space.</p>
<tdclass="cellrowborder"valign="top"width="55.76%"headers="mcps1.2.4.1.3 "><pid="p11976107144710"><aname="p11976107144710"></a><aname="p11976107144710"></a>Mounts devices. Every two parameters must be separated by only one space. Currently, supported flags include <strongid="b5512525411"><aname="b5512525411"></a><aname="b5512525411"></a>nodev</strong>, <strongid="b41014514541"><aname="b41014514541"></a><aname="b41014514541"></a>noexec</strong>, <strongid="b5101152543"><aname="b5101152543"></a><aname="b5101152543"></a>nosuid</strong>, <strongid="b20103555419"><aname="b20103555419"></a><aname="b20103555419"></a>rdonly</strong>, and optionally <strongid="b41045175420"><aname="b41045175420"></a><aname="b41045175420"></a>data</strong>.</p>
<tdclass="cellrowborder"valign="top"width="55.76%"headers="mcps1.2.4.1.3 "><pid="p4350121915488"><aname="p4350121915488"></a><aname="p4350121915488"></a>Starts services. <emid="i87951116544"><aname="i87951116544"></a><aname="i87951116544"></a>serviceName</em> must be contained in the <strongid="b379981145417"><aname="b379981145417"></a><aname="b379981145417"></a>services</strong> array.</p>
<tdclass="cellrowborder"valign="top"width="55.76%"headers="mcps1.2.4.1.3 "><pid="p13986141320510"><aname="p13986141320510"></a><aname="p13986141320510"></a>Loads other <strongid="b280561515549"><aname="b280561515549"></a><aname="b280561515549"></a>.cfg</strong> files. The maximum size of the target file (only <strongid="b105471717135416"><aname="b105471717135416"></a><aname="b105471717135416"></a>/patch/fstab.cfg</strong> supported currently) is 50 KB. Each line in the <strongid="b14853122910540"><aname="b14853122910540"></a><aname="b14853122910540"></a>/patch/fstab.cfg</strong> file is a command. The command types and formats must comply with their respective requirements mentioned in this table. A maximum of 20 commands are allowed.</p>
<tdclass="cellrowborder"valign="top"width="89.63%"headers="mcps1.2.3.1.2 "><pid="p1173818913714"><aname="p1173818913714"></a><aname="p1173818913714"></a>Name of the current service. The value cannot be empty and can contain a maximum of 32 bytes.</p>
<tdclass="cellrowborder"valign="top"width="89.63%"headers="mcps1.2.3.1.2 "><pid="p1073815910717"><aname="p1073815910717"></a><aname="p1073815910717"></a>Full path (including parameters) of the executable file for the current service. This is an array. Ensure that the first element is the path of the executable file, the maximum number of elements is 20, and each element is a string that contains a maximum of 64 bytes.</p>
<tdclass="cellrowborder"valign="top"width="89.63%"headers="mcps1.2.3.1.2 "><pid="p107387920711"><aname="p107387920711"></a><aname="p107387920711"></a>User ID (UID) of the current service process.</p>
<tdclass="cellrowborder"valign="top"width="89.63%"headers="mcps1.2.3.1.2 "><pid="p12738691479"><aname="p12738691479"></a><aname="p12738691479"></a>Group ID (GID) of the current service process.</p>
<tdclass="cellrowborder"valign="top"width="89.63%"headers="mcps1.2.3.1.2 "><pid="p12738691493"><aname="p12738691493"></a><aname="p12738691493"></a>Security context of the current service process (no need to set currently).</p>
<tdclass="cellrowborder"valign="top"width="89.63%"headers="mcps1.2.3.1.2 "><pid="p18548317195715"><aname="p18548317195715"></a><aname="p18548317195715"></a>Whether the current service process is a one-off process.</p>
<pid="p103571840105812"><aname="p103571840105812"></a><aname="p103571840105812"></a><strongid="b7898115614817"><aname="b7898115614817"></a><aname="b7898115614817"></a>1</strong>: The current service process is a one-off process. If the process exits, the init process does not restart it.</p>
<pid="p5831191431116"><aname="p5831191431116"></a><aname="p5831191431116"></a><strongid="b20971155820811"><aname="b20971155820811"></a><aname="b20971155820811"></a>0</strong>: The current service process is not a one-off process. If the process exits, the init process restarts it upon receiving the SIGCHLD signal.</p>
<pid="p378912714010"><aname="p378912714010"></a><aname="p378912714010"></a>Note: If a non-one-off process exits for five consecutive times within four minutes, the init process will no longer restart it at the fifth exit.</p>
<tdclass="cellrowborder"valign="top"width="89.63%"headers="mcps1.2.3.1.2 "><pid="p166448210816"><aname="p166448210816"></a><aname="p166448210816"></a>Whether the current service process is a key system process.</p>
<pid="p8572182712811"><aname="p8572182712811"></a><aname="p8572182712811"></a><strongid="b72917915010"><aname="b72917915010"></a><aname="b72917915010"></a>0</strong>: The current service process is not a key system process. If it exits, the init process does not reset or restart the system.</p>
<pid="p11861032111516"><aname="p11861032111516"></a><aname="p11861032111516"></a><strongid="b1074320101309"><aname="b1074320101309"></a><aname="b1074320101309"></a>1</strong>: The current service process is a key system process. If it exits, the init process resets and restarts the system.</p>
<tdclass="cellrowborder"valign="top"width="89.63%"headers="mcps1.2.3.1.2 "><pid="p489313618173"><aname="p489313618173"></a><aname="p489313618173"></a>Capabilities required by the current service. They are evaluated based on the capabilities supported by the security subsystem and configured in accordance with the principle of least permission. Currently, a maximum of 100 values can be configured.</p>
