El vie, 21-06-2013 a las 13:19 +0200, Fabio Erculiani escribió: > For me, the big selling points of eselect-init are: > > 1. as release engineer, i can prepare images that use either systemd > or openrc (at present time these are the two supported options) and do > it reliably, programmatically. > 2. as distro maintainer, i can roll out a migration path from openrc > to systemd (or vice versa). The properties of this migration path I am > looking for are reliability and "atomicity". Basically, once you move > logind/consolekit detection to runtime (and believe it or not, many > upstream just get it wrong), and have feature parity in the systemd > units available (wrt openrc initscripts), switching over is a matter > of 2 (soon 1) commands. > > Both of them are quite important, because there are scenarios in where > systemd fits better than openrc, and scenarios in where openrc is a > better fit (older kernels, production system with custom init scripts > that are not worth the porting, etc). > Making the switch between openrc and systemd easy is a big win (for > both developers, distro maintainers, users) and makes Gentoo more > attractive, but this is another topic... >
Thanks for the explanation. But I think that, currently, the only remaining "objection" is whether play with /sbin/init (that needs sysvinit to be changed if I don't misremember) or with /sbin/einit. Looks like mgorny has shown some problems on relying on "einit" instead of plain "init" regarding to fallback :/
