Re: runit pblms on Mandrake

[Laurent Bercot <ska-supervision@skarnet.org>]

> no,the reason is what you said below.the /package and /command directorys
> may be not stay at root partition.Although we can think /pacakge/admin/* 
> as the basic system packages,but what about others?like /package/prog?
> /package/host?Are they basic?So we have to take all the /package/*,at least
> all the binaries under /package at root partition?

 No, of course.
 You can have for instance /rootfs/package, located on the root partition,
/usr/local/package, located on another one, and /package being a set of
symlinks pointing to the right places. The command
  update-symlinks /package /rootfs/package /usr/local/package
will create the right links in /package.

 Remember: /package is only an _access_ path, not a physical location path.
Nobody cares where your files really are, as long as they can be
reliably accessed. You could even have the runit and runit-init binaries
on the root partition, and everything else, including the rest of the
runit package, in /usr/local - no problem as long as /package and /command
still provide the right access paths.


> good idea,we dont need *replace* /sbin/init,thanks!But maybe I use
> init=/sbin/runit-init in my /etc/grub.conf, :)

 Don't. Use init=/command/runit-init
         or init=/package/admin/runit/command/runit-init
in your /etc/grub.conf, and make sure it points to the actual runit-init
program.

-- 
 Ska