From 4448842bb141430e23498d5a969b5cefe8786e57 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Thu, 14 Apr 2016 13:21:19 +0000 Subject: - make s6-linux-init-maker write stage1 to dir/init instead of stdout - version: 0.1.0.0 --- doc/index.html | 19 ++++++++++------- doc/quickstart.html | 5 ++--- doc/s6-linux-init-maker.html | 50 +++++++++++++++++++++++++------------------- doc/upgrade.html | 18 ++++++++++++++++ 4 files changed, 61 insertions(+), 31 deletions(-) (limited to 'doc') diff --git a/doc/index.html b/doc/index.html index efcd308..9906135 100644 --- a/doc/index.html +++ b/doc/index.html @@ -50,15 +50,15 @@ a small FAQ.
  • A Linux-based system with a standard C development environment
  • GNU make, version 3.81 or later
  • skalibs version -2.3.8.0 or later
    • +2.3.10.0 or later
  • execline version -2.1.4.2 or later
    • +2.1.5.0 or later
  • s6-portable-utils version -2.0.5.3 or later
    • +2.0.6.0 or later
  • s6-linux-utils version -2.0.2.3 or later
    • +2.1.0.0 or later
  • s6 version -2.2.2.0 or later
    • +2.3.0.0 or later

    @@ -86,9 +86,14 @@ against the shared version of the skalibs library, it also becomes a

    Compilation

    diff --git a/doc/quickstart.html b/doc/quickstart.html index da47334..bd758b1 100644 --- a/doc/quickstart.html +++ b/doc/quickstart.html @@ -39,10 +39,9 @@ add the -d 1 option to the s6-linux-init-maker command line below.
  • As root, run: 
          rm -rf /tmp/s6-linux-init /tmp/init
-     s6-linux-init-maker /tmp/s6-linux-init > /tmp/init
-     chmod 0700 /tmp/init
+     s6-linux-init-maker /tmp/s6-linux-init
      mv /tmp/s6-linux-init /etc/
-     mv /tmp/init /sbin/
    • + ln -sf /etc/s6-linux-init/init /sbin/init
  • Reboot.
  • Congratulations! your machine is now running a s6-based init system.
    • diff --git a/doc/s6-linux-init-maker.html b/doc/s6-linux-init-maker.html index e2e0b2b..e82ce40 100644 --- a/doc/s6-linux-init-maker.html +++ b/doc/s6-linux-init-maker.html @@ -21,7 +21,12 @@

    s6-linux-init-maker reads configuration options on the command line, and outputs a directory to place in the -root filesystem as well as a script suitable as an init program. +root filesystem. That directory contains a script suitable +as an init program, as well as support file hierarchies to +get a complete +s6 +infrastructure running when the system is booted on that +script.

    @@ -58,7 +63,7 @@ machine - else the scripts will crash. [ -d dev_style ] \ [ -s env_store ] \ [ -e initial_envvar ] ... \ - dir > stage1 + dir

    @@ -81,35 +86,37 @@ tool can do it, as well as the GNU or busybox cp -a or mv comm

    - The stage1 script printed by s6-linux-init-maker on its -stdout is then suitable as an init program. The administrator should -copy it to /sbin/init and make it executable. + The basedir/init script +is then suitable as a "stage 1" init program, i.e. the first program +run by the kernel. The administrator should make a symbolic link +from /sbin/init to basedir/init; the +machine will then be ready to boot

    Boot sequence

    - When the kernel boots, it runs the stage1 script, and this is -what happens: + When the kernel boots, it runs the basedir/init script, +also known as stage 1. and this is what happens:

    @@ -158,7 +165,7 @@ getty is essentially to make it easier to debug if stage2 fails. There is nothing else. In particular, no filesystem has been mounted yet, including /proc and /sys; and no one-time initialization -has been performed. The point of stage1 is only to make it +has been performed. The point of stage 1 is only to make it possible to run stage2 with a logging infrastructure and a supervision infrastructure already available, and all the real machine and service initialization should happen in stage2. @@ -222,7 +229,8 @@ service manager.

    s6-linux-init-maker options