https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv en a blog about Debian and self-hosting Fri, 21 Aug 2015 12:29:00 +0000 PluXml https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1440160180-1 https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1440160180-1 "Systemd will eventually consume the alternatives." — mark Correction, Red Hat will eventually consume the alternatives. Everything else will be some kind of clones with a custom look (like Debian at the moment and the only thing it lacks to achieve that goal is a Debian Enterprise Edition.) Fri, 21 Aug 2015 12:29:00 +0000 P.G. https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1438903907-1 https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1438903907-1 Systemd will eventually consume the alternatives. Thu, 06 Aug 2015 23:31:00 +0000 mark https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1413809547-1 https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1413809547-1 @Ralf: why would anyone *not* remove “quiet” from the kernel command line (other than “using *buntu” ofc). I like to see what’s going on. Mon, 20 Oct 2014 12:52:00 +0000 mirabilos https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1413625428-1 https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1413625428-1 Odd, I've not seen that. I've got one computer using cryptsetup to manage an encrypted root, and a different one with only an encrypted /var (/home bind-mounts to /var/local/home) also with cryptsetup, neither of them have plymouth, and I don't get any interruptions when entering my passphrase under systemd. Sat, 18 Oct 2014 09:43:00 +0000 Karellen https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1413584608-1 https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1413584608-1 Hi tanguy, I have the same issue as you with systemd. I hame my /home LVM volume encrypted, and systemd does not integrate it very well through boot process. @Derek Having only /home encrypted saves me some CPU time on my old hardware ;) Fri, 17 Oct 2014 22:23:00 +0000 pywy https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1413579705-1 https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1413579705-1 That's weird, on my system systemd does not even print all these status messages. So even if it would ask the password later (I have the root encrypted), it shouldn't be a problem. Did you removem "quiet" from the kernel parameters? Fri, 17 Oct 2014 21:01:00 +0000 Ralf https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1413573743-1 https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1413573743-1 You only encrypt some of your drives. If your whole drive is encrypted, the initramfs must wait before systemd launches, and the password dialog is smooth. If you haven't encrypted your whole drive... Well, someone with access to your system could very well just subvert your root FS. Why haven't you encrypted your whole drive? Fri, 17 Oct 2014 19:22:00 +0000 Derek https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1413561438-1 https://tanguy.ortolo.eu/blog/article132/trying-systemd-back-to-sysv/#c1413561438-1 Luckily, I had already plymouth running before switching to systemd, so despite using cryptsetup, it worked just fine. Fri, 17 Oct 2014 15:57:00 +0000 Joachim Breitner