From 6f13cd197540af0bf5e87f87ab0e03548d9c5f64 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Sat, 27 Apr 2019 23:27:39 +0000 Subject: Doc fixes --- doc/s6-linux-init.html | 19 +++++++++++++------ 1 file changed, 13 insertions(+), 6 deletions(-) (limited to 'doc/s6-linux-init.html') diff --git a/doc/s6-linux-init.html b/doc/s6-linux-init.html index e8ab361..31014d6 100644 --- a/doc/s6-linux-init.html +++ b/doc/s6-linux-init.html @@ -52,12 +52,11 @@ If there is a discrepancy, the system might not boot.
  • -c basedir : read all its initialization data from basedir. If the data has not indeed been copied to basedir, the system will not boot.
    • -
  • -p initial_path : the value to -set the initial PATH environment variable to. +
  • -p initial_path : the initial value for +the PATH environment variable.
  • -s env_store : the place where to dump kernel environment variables.
    • -
  • -m initial_umask : the value of -the initial file umask.
    • +
  • -m initial_umask : the initial file umask.
  • -d dev_style : how /dev is handled on this system. 0 means a static /dev, 1 means devtmpfs but not automounted by the kernel at boot time, and 2 means @@ -130,8 +129,16 @@ the arguments given to rc.init.
    • as pid 1 and has spawned its early services - at least the catch-all logger, and the other services, including the early getty if it has been defined, are started in parallel and will be ready instantly. rc.init can then -perform stage 2 of the initialization process, i.e. the initialization -sequence per se. +perform stage 2 of the initialization process, i.e. the handoff to +the service manager. +

    + +

    Exit codes

    + +

    + s6-linux-init never exits. It spawns the rc.init script +and execs into s6-svscan, +which runs forever until the machine stops or reboots.

    Notes

    -- cgit v1.3.1