Bug#746578: Reasons to keep systemd-sysv as the first alternative
I conceptually dislike the user experience of switching init systems
because the user upgraded some random package that, from their
perspective, doesn't appear related to the init system. I feel like
switching init systems should be a more intentional action than that.
There is a variety of local customization that is init-system-specific,
and I'm dubious that we're going to be able to catch and warn about all of
it.
I've not made up my mind about the merits of switching init systems from
sysvinit to systemd during a dist-upgrade, but if we do that, I think we
should do it via some more deliberate and obvious method than pulling
systemd-sysv in via the dependency tree of some random package. The
partial upgrade UX for that is really bad, IMO.
--
Russ Allbery (rra@debian.org) <http://www.eyrie.org/~eagle/>
Reply to: