Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #212661
| From | <tomas@tuxteam.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Systemd start that won't stop |
| Date | 2019-08-11 23:40 +0200 |
| Message-ID | <yu3Jf-3GD-1@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <ythuV-5Ta-1@gated-at.bofh.it> <ytkCt-7Mj-1@gated-at.bofh.it> <yu08G-1nW-21@gated-at.bofh.it> <yu0BH-1NS-3@gated-at.bofh.it> <yu2WR-39g-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On Sun, Aug 11, 2019 at 11:27:31PM +0300, Reco wrote: > Hi. > > On Sun, Aug 11, 2019 at 07:55:12PM +0200, tomas@tuxteam.de wrote: [...] > > 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. Ah, thank, Reco. That makes sense... > 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. Yes, I now remember some folks here complaining that they couldn't enter their passphrase... > In short, plymouth can fix problems, but you have to work hard to get > them. I see ;-) Cheers -- t
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Systemd start that won't stop Curt Howland <Howland@priss.com> - 2019-08-09 17:40 +0200
Re: Systemd start that won't stop Kenneth Parker <sea7kenp@gmail.com> - 2019-08-09 18:10 +0200
Re: Systemd start that won't stop Étienne Mollier <etienne.mollier@mailoo.org> - 2019-08-09 19:00 +0200
Re: Systemd start that won't stop Curt Howland <Howland@priss.com> - 2019-08-09 20:10 +0200
Re: Systemd start that won't stop Étienne Mollier <etienne.mollier@mailoo.org> - 2019-08-09 21:00 +0200
Re: Systemd start that won't stop Richard Hector <richard@walnut.gen.nz> - 2019-08-10 09:40 +0200
Re: Systemd start that won't stop Sven Joachim <svenjoac@gmx.de> - 2019-08-09 21:40 +0200
Re: Systemd start that won't stop Étienne Mollier <etienne.mollier@mailoo.org> - 2019-08-09 22:10 +0200
Re: Systemd start that won't stop Greg Wooledge <wooledg@eeg.ccf.org> - 2019-08-09 22:30 +0200
Re: Systemd start that won't stop Étienne Mollier <etienne.mollier@mailoo.org> - 2019-08-09 23:20 +0200
Re: Systemd start that won't stop Sven Joachim <svenjoac@gmx.de> - 2019-08-09 23:00 +0200
Re: Systemd start that won't stop Felix Miata <mrmazda@earthlink.net> - 2019-08-09 23:30 +0200
Re: Systemd start that won't stop Mart van de Wege <mvdwege@gmail.com> - 2019-08-11 19:50 +0200
Re: Systemd start that won't stop <tomas@tuxteam.de> - 2019-08-11 20:20 +0200
Re: Systemd start that won't stop Mart van de Wege <mvdwege@gmail.com> - 2019-08-11 22:50 +0200
Re: Systemd start that won't stop <tomas@tuxteam.de> - 2019-08-11 23:40 +0200
Re: Systemd start that won't stop Reco <recoverym4n@enotuniq.net> - 2019-08-11 22:50 +0200
Re: Systemd start that won't stop <tomas@tuxteam.de> - 2019-08-11 23:40 +0200
Re: Systemd start that won't stop David Wright <deblis@lionunicorn.co.uk> - 2019-09-17 20:50 +0200
csiph-web