copy runit-init to /sbin/init or not

[Alex Efros <powerman@powerman.asdfGroup.com>]

Hi!

> * Gerrit Pape <pape@smarden.org> [2006-02-13 14:44:31 +0000]:
> > Yes, runit-init must be /sbin/init.  It's that /sbin/init on unix is not
> > only used as process 1, but also as command line interface while the
> > system is up (e.g. 'init 0', 'init 6').  With runit, the process no 1
> > duties are implemented in the runit program, and the cli in runit-init.
> > runit-init is installed as /sbin/init, and if it sees itself started
> > with pid 1, it immediately replaces itself with /sbin/runit, the process
> > no 1 implementation.  If it's not running as pid 1, it's the command
> > line interface to signal the (currently as process no 1 running) runit
> > process.

Do you aware of any software which run 'init [0|6]' or 'halt' or 'reboot'?
For now I've seen these commands executed only manually by root and by
acpid daemon.

I've problems with installing runit-init as /sbin/init on my Gentoo - this
is because from time to time while upgrading overall system 'sysvinit' package
become upgraded and it replace /sbin/init. If I forget to replace it
by runit-init manually again, I got surprise on next reboot. :-(

Currently I work around this issue this way:
- /sbin/{init,halt,reboot} is sysvinit's
- kernel boot with param init=/sbin/runit-init
- there aliases configured in /root/.bashrc:
    alias reboot='/sbin/runit-init 6'
    alias halt='/sbin/runit-init 0'
  (I usually use reboot|halt, not init 0|6, but alias for init also can be
  added if needed)
- acpid configured to run '/sbin/runit-init 0' in it /etc/acpi/default.sh

-- 
			WBR, Alex.