Re: "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage"

[Willy Tarreau <w@1wt.eu>]

On Sun, Oct 07, 2007 at 08:47:52PM +0200, Rene Herman wrote:
> On 10/07/2007 06:12 PM, Ingo Molnar wrote:
> 
> >* Oleg Verych <olecom@flower.upol.cz> wrote:
> 
> >>Coloring isn't useful. If it was, it would be implemented ~16 years
> >>ago.
> >
> >Congratulations, this is the most stupid argument i've ever read on 
> >lkml.
> 
> "Ay. World is finished. Everyone can go home and watch Friends reruns now."
> 
> 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. And fortunately,
the mainstream distros still provide the option to boot in text mode.

> Sure, that in itself needn't necesarily be of concern to anyone who, err, 
> is not concerned but any such colouring feature appearing when there's only 
> a smathering of people left that still cares about the VGA console in the 
> first place really isn't all _that_ far out as an argument...

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.

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

I would say that while I'm not particularly fond of flashy colors
everywhere, I think that being able to use colors to indicate particular
actions in progress or conditions can be a good thing. RAID errors,
devices disabled due to command-line parameters, and general anomalies
which can cause a hang or panic a few line laters are worth coloring.
And I don't believe in userland's help here, because for that type of
messages, the indication should be returned immediately. For instance,
anyone who has experienced read errors on and IDE disk knows that it
can literally take hours/days to boot, after displaying thousands of
messages. Here, having the ability to see that no IRQ was assigned or
something like this could help.

Regards,
Willy

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