Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #212659

Re: Systemd start that won't stop

Show all headers | View raw

	Hi.

On Sun, Aug 11, 2019 at 07:55:12PM +0200, tomas@tuxteam.de wrote:
> On Sun, Aug 11, 2019 at 07:11:19PM +0200, Mart van de Wege wrote:
> > Felix Miata <mrmazda@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

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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