https://bugzilla.novell.com/show_bug.cgi?id=728947
https://bugzilla.novell.com/show_bug.cgi?id=728947#c13
--- Comment #13 from Ruediger Meier
This will not happen due the simple reason that *most* people expect that insserv will enable a service even if provided by a systemd service unit.
On the other hand the only reason why some users stick with sysvinit at all is that they want the old stable non-patched thing. It's a pity that deploying systemd also affected sysvinit.
This enforces tht both systemd and SysVinit will be hold in sync and the user is able to switch the init daemon.
Couldn't it be synced somehow when the user is actually switching? If you do a fresh systemd install then it starts from scratch too. Morever if user is using whatever other tool to set init links then they are not in sync anyway. What about conflicting systemd-sysvinit and sysvinit-init packages and also update-alternative insserv? BTW getting rid of the "systemd/sysvinit sync" could also make it possible to remove a lot of the last systemd deps. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.