-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 06/01/12 03:16 AM, Alec Warner wrote: > Perhaps keep 'init' as a fairly simple codebase and run 'systemd' > as pid 2 and they can chat with each other (over dbus?) >
I seriously hope that was a troll... the whole point of systemd, as I understand it, is to entirely replace sysvinit+whatever-rc-script-system you have. To instead make systemd only an openrc alternative, and then trash sysvinit by making it communicate over dbus, would be a more horrible kludge. Addressing your point, though, I think it might be desirable to perhaps strip out all of the actual direct service-control stuffs from systemd and make it more of a sysvinit replacement -- that is, have it simply launch/control services via init.d/ shell scripts (or whatever, as long as they're external) instead of relying on internal service code within the systemd binary itself. And I expect that this wouldn't really be that hard to do, given that systemd already has to support external service scripts right? That said, I don't think I ever intend to migrate to systemd for my server systems -- sysvinit + baselayout-1-rc is still working just fine for me; I haven't even migrated most of them to openrc yet. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iF4EAREIAAYFAk8HExcACgkQAJxUfCtlWe07kQEA08+XUqQbAybxlmfiPI6QCcUN f9kQX3arCKshaIou4M0A/j0IXAi/uZlg3a7pZ9+HXo2fwcpz84J7PKQSwKr20mrq =sC3I -----END PGP SIGNATURE-----
