Hi. Unless I'm mistaken, this could be useful in the context of Docker containers, where a few people have advocated the use of runit inside containers where Debian packages are installed.
I think baseimage-docker [0] is one such system, unless it has evolved since I last checked. FWIW. Best regards, [0] http://phusion.github.io/baseimage-docker/ P.S.: I once tried to adapt baseimage-docker to Debian, but have long neglected to try and maintain a Debian "fork". Gerrit Pape <[email protected]> writes: > This essentially is a reintroduction of the package "runit-run", which > was added to Debian end of 2002, and removed on request of the release > team end of 2010, with the package name changed. Since then, a backward > compatibility feature for running sysv rc scripts was added, ideally to > be replaced by runit service directories eventually. > > Description: a UNIX init scheme with service supervision > runit is a replacement for SysV-init and other init schemes. It runs on > Debian GNU/Linux, *BSD, MacOSX, and Solaris, and may be easily adapted > to other Unix operating systems. runit implements a simple three-stage > concept. Stage 1 performs the system's one-time initialization tasks. > Stage 2 starts the system's uptime services (via the runsvdir program). > Stage 3 handles the tasks necessary to shutdown and halt or reboot. > . > See http://smarden.org/runit/ for more information. > . > This package replaces the /sbin/init program and configures runit to run > as process no 1 after the next reboot. > License: 3-clause BSD > > You can take a look at the current status through > git clone http://smarden.org/git/runit-init.git/ > > Regards, Gerrit. -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
