From 76ec0723593b27918e37d9cb1d1965b9b57b4c52 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Wed, 17 Jun 2015 20:03:10 +0000 Subject: - add links to s6-linux-init - version: 2.1.4.0 --- doc/s6-svscan-1.html | 26 ++++++++++++++++++++++---- 1 file changed, 22 insertions(+), 4 deletions(-) (limited to 'doc/s6-svscan-1.html') diff --git a/doc/s6-svscan-1.html b/doc/s6-svscan-1.html index d88b64e..2f46ee6 100644 --- a/doc/s6-svscan-1.html +++ b/doc/s6-svscan-1.html @@ -18,6 +18,13 @@

How to run s6-svscan as process 1

+

+ Since 2015-06-17, if you're a Linux user, you can use the +s6-linux-init +package to help you do so! Please read this documentation page first, +though, it will help you understand what s6-linux-init does. +

+

It is possible to run s6-svscan as process 1, i.e. the init process. However, that does not mean you can directly boot @@ -26,6 +33,8 @@ your stock init does. Replacing the init process requires a bit of understanding of what is going on.

+

A working example: s6-linux-init

+

The three stages of init

@@ -126,12 +135,21 @@ needed. Fortunately, those processes are very easy to design! The only difficulty here is that they're heavily system-dependent, so it's not possible to provide a stage 1 init and a stage 3 init that will work everywhere. s6 was designed to be as portable as possible, and it should run on virtually -every Unix platform; but outside of stage 2 is where portability stops, and -the s6 package can't help you there. +every Unix platform; but outside of stage 2 is where portability stops. +

+ +

+ The s6-linux-init +package provides a tool, s6-linux-init-maker, to automatically +create a suitable stage 1 init (so, the /sbin/init binary) for +Linux. +It is also possible to write similar tools for other operating systems, +but the details are heavily system-dependent.

- Here are some tips though. + For the adventurous and people who need to do this by hand, though, here are +are some general design tips.

@@ -205,7 +223,7 @@ init a script.

Of course, most people will use the shell as scripting language; however, I advocate the use of -execline +execline for this, and not only for the obvious reasons. Piping s6-svscan's stderr to a logging service before said service is even up requires some tricky fifo handling that execline can do -- cgit v1.3.1