Re: fsck progress not shown on boot with systemd as pid 1
On Fri 25 Jul 2014 at 16:02:18 -0400, The Wanderer wrote:
> On 07/25/2014 03:33 PM, Michael Biebl wrote:
>
> > Hi,
> >
> > Am 25.07.2014 20:27, schrieb Steven Post:
> >
> >> I'm running Jessie (lagging about 5 days behind with the updates)
> >> and use systemd-sysv. Today I noticed that there is no visual
> >> feedback from fsck when checking an ext4 filesystem at boot time.
> >> Since it appears the system is stuck (apart from the HDD LED) I
> >> would consdider this a bug. Is this known? I wanted to check the
> >> list first, especially since the system not fully up-to-date,
> >> before filing a bug report. I quick search didn't bring up any
> >> results.
> >
> > If the system is booted with the "quiet" kernel command line option,
> > no messages are shown by systemd.
> > You can either remove "quiet" from the kernel command line or use
> > the
> > systemd.show_status=true|false
> > systemd.sysv_console=true|false
> > systemd.log_level=
> > systemd.log_target=
> > boot options to control that in a fine grained manner.
>
> Is there any plan to do either of these things in the Debian-default
> configuration (and possibly update existing installs to match, if
> unmodified)? Or is the plan for the Debian-default boot-messages
> behavior to change with a switch to systemd?
With sysvinit the default at booting is for the screen messages to fly
past at a bewildering speed and then for the screen to be cleared by
agetty. Nobody particularily complains about this behaviour. Unless
you have an excellent visual memory you are in the dark as regards what
happened.
I'm trying to get to grips with what you envisage for a change in the
"Debian-default boot-messages behavior".
Reply to: