Fwd: Using runit-init on debian/Jessie in place of sysvinit/systemd

From: toki clover <tokiclover_at_gmail.com>
Date: Fri, 2 Jan 2015 01:31:46 +0100

---------- Forwarded message ----------
From: toki clover <tokiclover_at_gmail.com>
Date: 2015-01-02 1:30 GMT+01:00
Subject: Re: Using runit-init on debian/Jessie in place of sysvinit/systemd
To: Luke Diamand <luke_at_diamand.org>

First, it's a bit crazy to use runit for init+service management entirely

- It's completely crazy to supervise every service because; first, every
won't fit in if it's not a daemon; second supervising every daemon is
- Second, runit (or s6 for that matter) lack any decent service dependency,
actually both completely ignore the problem (athough s6 may change this in
in a near futur.)
- Third, do not forget the overhead of supervision (an extra instance per

Second, stuffing stage 1 `/etc/runit/1' is a bad idea because stage 1 is
sensible... any service that hangs in the foreground will hang booting
because C-ALT-DEL signal is inactive (see this page for more details

So, I would recommend using rc, or even better OpenRC (which is available
in Debian based OS) to take care of service dependencies management and
use service supervision for agetty (and sshd and the likes if necessary.)
(There is a complete solution with runit+OpenRC in that thread.)

That forums thread has a dangerous implementation with a stuffed stage 1
which I split to have only sysinit related services in it and then use
stage 2
to fully boot the system and brings it to a desired runlevel. This is far
safer because a tty will be available to fix anything broken if need be.

Stuffing stage 1 is suicidal...

Good luck.

Error 404: gentoo user <0123456789> was not found
Received on Fri Jan 02 2015 - 00:31:46 UTC

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