On Mon, May 5, 2014 at 5:40 PM, Tollef Fog Heen <tfh...@err.no> wrote: > ]] Zack Weinberg >> Fundamentally what I want is a bulletproof procedure for reverting to >> sysvinit in case something goes wrong. > > Sounds like you're arguing that sysvinit-core should no longer ship > /sbin/init, then, so systemd-sysv doesn't have to conflict with it.
Wouldn't that make the sysvinit implementation of /sbin/init completely unavailable? This is an earnest question. I do not have access to package contents right now. Note that coinstallability is not enough -- the bulletproof procedure (e.g. "update-init-system") must also be implemented, shipped, and documented. zw -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
