El lun, 03-06-2013 a las 00:35 +0200, Luca Barbato escribió: [...] > To not make this a waste of time here a summary of the whole thing: > > - eselect init will be opt-in for the time being, people can be left on > their own tools if the want it > - the default init will stay sysvinit. Discussion ongoing if is better > to have it installed in a secondary fallback path is open (e.g. /bin/init). > - I still need to send patches to busybox and sysvinit upstream to add a > command line switch to locate the inittab. > - people wanting to switch init or enable/disable init addons using > eselect init might have to refer to /sbin/einit or such custom path > (assuming we fail to come to an agreement regarding /bin/init) > > The wrapper in /sbin/init is mostly needed to get to the point of a > clean reboot. > > The first time you boot on a new system it is executed picking the new > init and just that. > > For addons such as bootchart2 and e4rat it would do slightly more. > > Assuming upstream doesn't accept custom paths for the inittab, for my > specific usecase I might bake something that would remount r/w and pivot > the inittabs. > > Anybody willing to do something more extreme could even consider having > /sbin/init as a symlink and have the boot-time configuration switch the > symlink, thus making the whole script run just a single boot per switch. > > Not necessary but surely feasible. > > lu > >
Thanks for the summary :)
