Hi. On Sun, Aug 11, 2019 at 07:55:12PM +0200, to...@tuxteam.de wrote: > On Sun, Aug 11, 2019 at 07:11:19PM +0200, Mart van de Wege wrote: > > Felix Miata <mrma...@earthlink.net> writes: > > > > > Curt Howland composed on 2019-08-09 13:53 (UTC-0400): > > > > > >> plymouth-quit-wait.service > > > ... > > >> I have no idea what a "plymouth" is. > > > > > > Several things it brings to the table: > > > 1-avoids /dastardly/ "flicker" on mode switching during startup > > > 2-bling/eye candy during startup > > > 3-bloats initrd > > > 4-encryption handling > > > 5-yet another tool for systemd to disrupt startup/shutdown > > > > > And beyond the FUD: > > > > 6. Make sure that the console is sane when you try to provide things > > like LUKS passphrases; the default bootup console will happily overwrite > > the prompt [...] > > Huh? Under what conditions does this happen?
Unusual ones. Put several encrypted devices into crypttab(5) with "none" option *and* make sure that none of them are mounted by initramfs scripts. Or put systemd into initramfs like they do in RHEL. In such setup systemd will ask you to enter several passphrases at same time. If you're using a single encrypted device which is setup by conventional initramfs scripts - there's no need for plymouth as there's nothing to fix. Everything works as intended. For me, at least. In short, plymouth can fix problems, but you have to work hard to get them. Reco
