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: <47093942.3090104@keyaccess.nl>
Date:	Sun, 07 Oct 2007 21:53:38 +0200
From:	Rene Herman <rene.herman@...access.nl>
To:	Willy Tarreau <w@....eu>
CC:	Ingo Molnar <mingo@...e.hu>, Oleg Verych <olecom@...wer.upol.cz>,
	Jan Engelhardt <jengelh@...putergmbh.de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>,
	Krzysztof Halasa <khc@...waw.pl>,
	Medve Emilian-EMMEDVE1 <Emilian.Medve@...escale.com>,
	Helge Deller <deller@....de>
Subject: Re: "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:'
 usage"

On 10/07/2007 09:13 PM, Willy Tarreau wrote:

> On Sun, Oct 07, 2007 at 08:47:52PM +0200, Rene Herman wrote:

>> But well, there actually have been worse arguments given that VGA console 
>> is getting less and less important. I recently did a perusal of alternative 
>> distributions and didn't find a single one that didn't default to having a 
>> splash screen hide the kernel during boot (and if I'm not mistaken, only 
>> one of them provided me with the option during installation to not boot 
>> into X immediately afterwards).
> 
> I don't recall having seen any splash screen on Slackware.

Indeed, but that's the distribution I use and considered switching away 
from. Just my luck eh? :-\

> There are two distinct populations :
>   - those who are afraid of boot messages and prefer "splash" screens.
>     Those people are most common users, grown in non-IT environments. They
>     are happy to see a big logo on their BIOS to hide important boot errors,
>     and they are the ones who would never have imagined that pressing Escape
>     during the boot of windows 3.1/95 provided them with the full text
>     messages. Basically, they want to ensure they will never have to worry
>     about things they don't understand.

Nor want to understand, often.

>   - those who are troubleshooting their system in the early stages (kernel,
>     filesystems, network, services, ...). These ones *need* boot messages.
>     And there, depending on the hardware, sometimes the FB is better because
>     it shows larger lines, sometimes it's worse because the scrollback is
>     limited by too low memory.
> 
> I personally fit in the second category. And I'm sure most people on this
> list do.

As do I ofcourse. An operating system kernel development list might provide 
for a fairly non-average balanced population of "am / am not interested in 
the inner workings of computers". Given that most everyone these days uses a 
computer, it's still a really small percentage though -- and as evidenced by 
the bootsplash thing, even of Linux users (and I've in fact heard real-life 
people say they disliked the noisy Linux bootup due to "all those errors").

> I would be miserably sad if I couldn't get my boot messages anymore. It
> already irritates me a lot to loose the ones displayed before switching
> to frame-buffer when a hang happens just afterwards...

Oh quite. I use VGA console myself. But not being able to get to the bootup 
messages anymore even for people who do care is not the issue. It's about 
finding it a bit hard to get excited about colourization when the "obvious" 
way forward is so much more graphically oriented.

As also commented in another reply just now, ways forward also tend to have 
their problems but this kind of "innovation" takes me back to the time when 
our favorite bulletins board adopted ANSI colours. Today, that seems just a 
tad pathetic...

Again, it might not hurt any either, but sheesh.

Rene.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ