On Tue, Sep 9, 2014, at 09:11, Samuel Thibault wrote: > > You cannot have an MTA without configuring it, and nobody even tried to > > implement auto-migration of the old default mailer's configuration to the > > new one. Also, we didn't switch to a different default mailer because the > > new one offered a heap of features and infrastructure which the other > > lacked. None of this applies to systemd. > > This does apply to systemd too. > > When I got "upgraded" to systemd on july, my system was completely > misbehaving for several reasons related to my configuration: > > - I had an ISO mount in my fstab, whose file didn't exist any more, > sysvinit never complained about it, systemd just stopped at boot. > - I had several bind mounts, forming loops, which has never been a > problem for sysvinit, but it made systemd take ages to boot & shutdown > because it'd crazily bring thousands of lines in /proc/mounts, details > in #755674. > - I had tweaks in /etc/inittab to get the gettys earlier than > daemon starts, in case those get stuck etc., this does not work any > more with systemd. > - I had tweaks in /etc/inittab to have more gettys on the text console, > this does not work with systemd any more. > - I had tweaks in /etc/inittab to shutdown instead of reboot when I > press ctrl-alt-backspace, this does not work with systemd any more.
And you are saying that you can do all those tweaks, but you cannot pin systemd-sysv to not install? Let's just document the way how to prevent systemd-sysv to install in release notes and switch the default init to systemd as Debian maintainers who would like to keep their sanity would do. Ondrej -- Ondřej Surý <ond...@sury.org> Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- 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/1410256058.2294779.165322957.7f81e...@webmail.messagingengine.com
