Re: fsck progress not shown on boot with systemd as pid 1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 08/02/2014 03:15 PM, Brian wrote:
> On Sat 02 Aug 2014 at 12:24:46 -0600, Bob Proulx wrote:
>
>> Brian wrote:
>
>>> 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.
>>
>> Just for the record I complain about that behavior. I don't like
>> the fancy tty colors and always disable them. I don't like the
>> screen clearing those away and so I always set the getty --noclear
>> option. The problem is that while there may be complaints like mine
>> I don't see them changing anything.
>
> Upstream for agetty responded to concerns about security from users,
> some of whom apparently had the compliance police breathing down
> their necks. My view on such idiocy is probably not for this list.
> The --noclear option rules here too.
Where do you set this, exactly? /etc/inittab ? (If so, what about for
systemd? /etc/inittab is much about runlevels, which systemd doesn't use
AFAIK.)
I don't generally have much problem with reading the boot messages as
they scroll past, but my short-term memory isn't always as sharp as I'd
like, so I'd like to be able to refer back to them after they scroll
off-screen anyway.
> Many people use a DM and will not see the boot messages but suddenly
> we have complaints about systemd doing what sysvint has done for some
> time.
Er... what exactly are you referring to?
I don't see "print messages to the console, possibly fast enough to be
hard to read, then clear the screen" as being even close to the same
thing as "don't print messages to the console".
What exactly is it here that systemd is doing which sysvinit has done
for some time?
- --
The Wanderer
Secrecy is the beginning of tyranny.
A government exists to serve its citizens, not to control them.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBCgAGBQJT3YgAAAoJEASpNY00KDJrIJ8P/0b56+maAkugM2CIvuo5voQc
1Wa0pxJRcTjiLFSO9A7QYSVeANpLBFQbsEYm/cNnaQy6jgxPPaCFVD4IQp7bHEpo
61tQjJLH7KMNW1m/RVA6Ad3TiN+BL1t6QZon8sQOYlFOiJS9zi1sw2aDxmdedIF7
1PWXePXtFVhc6OhUYAtHVWlPp/l9YfhlIvdTguVwHV0Q1R3CzsyDMQUyJ/Q395Zj
n1W2vpQgmyw5gR3YZjVmX3gKvMWSW1Zz6AQMtAq3k2V2cp+WOqO3hJluezXTNZki
ATH2uTNBr0/p6fneUcHhMpzrpok0v1Kzm1KPKbk/RgqTxkdGtFWBENdUNDSpWS0N
WmtCJlxWTidhEmyWcDcrzOO9dIXi1uul8WvLj5YAF6Sjwsjpfi9Z1MyBBsl4WAX/
4MvCFKUTTbD46ZUF/fJHKWNbXRlb0lsc8DCanjfQuuhnJyvAy0e/28e4DyhhTltl
IKwXNQgp4iSn3XxpAmEUkVyIG9Jg6T9pxCu6oUds9ACVA3ofh7hfD4UMXU2aamor
y+qoJdn0TP7yDYpl3IY9mXnuoGoiVYDPtvCE1zzyhWP7r5im+RdM43rGjYvyoY6h
qI1wBiXo3tnjOjdWmNCpFxaZLcFw8o0CsB2Fqvvt3THXKTumuxVJVAFa5QFA+G+5
e50FZG1tTZ1YxJTWsWlT
=o3TI
-----END PGP SIGNATURE-----
Reply to: