Dnia 2013-06-20, o godz. 23:16:00 William Hubbs <willi...@gentoo.org> napisał(a):
> On Fri, Jun 21, 2013 at 04:39:59AM +0200, Michał Górny wrote: > > Dnia 2013-06-20, o godz. 15:56:09 > > William Hubbs <willi...@gentoo.org> napisał(a): > > > > > On Thu, Jun 20, 2013 at 12:16:36PM +0200, Fabio Erculiani wrote: > > > > There is a new version of eselect-init in the systemd-love overlay to > > > > play with. > > > > The new version saw the following major changes: > > > > > > > > - the /sbin/init (aka the symlink that eselect-init handles) can be > > > > changed to whatever one wants through make.conf [1] (this is a compile > > > > time option, as documented in the eclass) > > > > > > Why do we need to mess with /sbin/init at all? > > > > Yes, we do because we don't want sysvinit randomly getting run > > as fallback and messing with our systems. > > I don't understand what you are saying here. > > If eselect-init installs the wrapper as /sbin/einit, we don't have to > touch /sbin/init at all, then, the only thing someone would have to do > is to add an entry to their boot loader with init=/sbin/einit on the kcl > to use it. But *if* the wrapper fails to run somehow, e.g. becomes broken, the kernel will fallback to the standard location. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
