Simon McVittie <s...@debian.org> writes: > It might actually be nicer to move the real sysvinit binaries to a > non-conflicting location in sysvinit (or a new non-Essential > sysvinit-bin or something, if it's desirable to keep the Essential > sysvinit package as a metapackage depending on any supported pid 1 > implementation), and have both sysvinit-core and systemd-sysv consist > entirely of symlinks. That would let cautious systemd users keep the > sysvinit binaries around, and boot with init=/usr/lib/sysvinit/init if > something went horribly wrong with systemd.
Ah, sort of like what you can do if you install the regular systemd package, but for sysvinit rather than systemd, so that they're both somewhat parallel in having symlink packages and binary packages? That seems like a good idea. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87oaz6wzk0....@windlord.stanford.edu
