lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 09 Nov 2017 13:42:51 +0100
From:   Takashi Iwai <tiwai@...e.de>
To:     "Pavel Machek" <pavel@....cz>
Cc:     "Max Staudt" <mstaudt@...e.de>, <michal@...kovi.net>,
        <b.zolnierkie@...sung.com>, "Michal Srb" <MSrb@...e.com>,
        "Oliver Neukum" <ONeukum@...e.com>,
        "Stefan Dirsch" <sndirsch@...e.com>, <linux-fbdev@...r.kernel.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [RFC 00/14] Kernel based bootsplash

On Thu, 09 Nov 2017 12:56:55 +0100,
Pavel Machek wrote:
> 
> Hi!
> 
> > Dear fbdev and fbcon developers,
> > 
> > Could you please voice your opinion on the following patch series?
> > 
> > 
> > This series adds simple bootsplash functionality on top of fbcon.
> > 
> > A (simple!) kernel based bootsplash allows system integrators to show an
> > earlier and more reliable bootsplash, completely hiding the kernel's
> > text output and VT (the 'quiet' option still displays warnings and a
> > blinking cursor).
> 
> "More reliable bootsplash" seems like an anti-goal. More reliable boot
> should be the goal...
> 
> You should be able to display nice splash screen from initrd...
> 
> We may want to fix the blinking cursor.
> 
> But if there are warnings, it is better to see the warnings then to
> hide them. If root filesystem can't be mounted (for example) it is
> good to know the reason, not to stare at the blank screen (or at boot splash).

In theory, we can put a bootsplash_disable() call automatically when
the certain level of kernel message appears, too.  It's a question
whether such behavior should be dynamically configurable or not,
though.

BTW, one thing that is bad with quiet boot option is that it hides
always messages and shows only errors.  With this bootsplash scenario,
you can boot without quiet option.  Once when the splash turned off
(either by user action like key input or by some kernel trigger),
you'll see the whole messages, thus have far more information there.


thanks,

Takashi

Powered by blists - more mailing lists