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  linux-cve-announce  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]
Message-ID: <20171109115655.GA18436@atrey.karlin.mff.cuni.cz>
Date:   Thu, 9 Nov 2017 12:56:55 +0100
From:   Pavel Machek <pavel@....cz>
To:     Max Staudt <mstaudt@...e.de>
Cc:     b.zolnierkie@...sung.com, linux-fbdev@...r.kernel.org,
        tiwai@...e.com, oneukum@...e.com, msrb@...e.com, sndirsch@...e.com,
        michal@...kovi.net, linux-kernel@...r.kernel.org
Subject: Re: [RFC 00/14] Kernel based bootsplash

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).

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ