What we could add is a --disable switch which makes
units/systemd-initctl.{socket,service} and src/initctl/ conditional so
distros that don't need it anymore can disable it (or make it disabled
by default and let distros which need it enable it).Would that work for you, Lennart? 2015-09-23 1:17 GMT+02:00 Michael Biebl <mbi...@gmail.com>: > 2015-09-23 0:45 GMT+02:00 Lennart Poettering <lenn...@poettering.net>: >> On Wed, 23.09.15 00:38, Michael Biebl (mbi...@gmail.com) wrote: >> >>> Hi, >>> >>> yes, in Debian we'll need /dev/initctl support for at least another >>> release cycle so users can switch between the init system and safely >>> reboot (in both directions). >> >> How does Debian switch between the init systems? Couldn't you just use >> the right client for the right init system? > > Well, you can't replace the running sysvinit instance with systemd > (and vice versa). > That's why we need the sysvinit tools to talk to systemd via > /dev/initctl and the systemd tools to talk to sysvinit. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
