Re: initialization vs supervision

From: Joan Picanyol i Puig <>
Date: Sun, 27 Jul 2014 16:30:10 +0200

* Laurent Bercot <> [20140727 00:53]:
> On 26/07/2014 20:47, Joan Picanyol i Puig wrote:
> >What "tricky" responsabilities are you thinking of for /sbin/init that
> >would make it Linux specific?
> s6-svscan wants a read-write directory to run in, and another to
> run its logger in. I definitely want to support read-only root
> filesystems, and it's too early to mount disks, so a tmpfs has to
> be created - this is system-dependent. If you have a way to do
> that in a system-agnostic way, I'm *very* interested. :)

No magic wand here, I just see it as scripts all the way down...

Creating and mounting a tmpfs and bringing up the network look pretty
much the same to me: initialization tasks orchestrated by scripts
invoking userland binaries. At this point in booting, if something fails
it's watchdog time...

Regarding read-only root fs, isn't it just a matter of restarting
svscan's logger pointing to stable storage once it is up & running?

Received on Sun Jul 27 2014 - 14:30:10 UTC

This archive was generated by hypermail 2.3.0 : Sun May 09 2021 - 19:44:18 UTC