On 14/10/14 14:33, Miles Fidelman wrote:
Which brings us back to how upgrades and new installs will be handled - will there be an option to go right to sysvinit-core, or will we have to manually uninstall systemd and anything that depends on it? Getting all the metapackages and dependencies right could be a real pain.
For *upgrades*, my understanding (as a user) is that you will be able to go straight to sysvinit-core by explicitly installing it before you invoke apt-get upgrade. For a belt-and-braces approach, you could also add an APT configuration fragment[0] pinning systemd-sysv to not be installable (so that *whatever* APT does, it won't involve systemd-sysv getting installed).
I don't know what the process is expected/intended to be for new installations where a non-default init system is desired.
[0] I've seen the relevant fragment posted recently, but I can't remember where and I don't remember the exact contents.