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

Willy Tarreau
2007-10-08T03:31:39Z

On Sun, Oct 07, 2007 at 09:56:09PM +0200, Jan Engelhardt wrote:
>
> On Oct 7 2007 21:13, Willy Tarreau wrote:
> >There are two distinct populations :
> > - those [...]
> > who would never have imagined that pressing Escape
> > during the boot of windows 3.1/95 provided them with the full text
> > messages.
>
> This is news to me. DOS always showed messages, and under Win95,
> it was either F8 or removing logo.sys. I did troubleshoot it ;-)

You remember that you could start them both from DOS by typing "win" ?
If you hit ESC during the first seconds when the logo showed, you could
get back to text mode to see the messages.

> > - those who are troubleshooting their system [...]
> >
> >I personally fit in the second category.
> >
> >I would say that while I'm not particularly fond of flashy colors
> >everywhere
>
> I have to agree so really. Just because there's a color option for
> everything does not mean one should use it.
>
> In fact, I moved away[2] from the default Midnight Commander styling
> because it's just - as Dave calls it - salad colors[1].

I found them "fun", it reminded me of the DOS-version of borland C, 15
years ago :-)

> Some is good, as long as it is not excessive. While I could imagine that
> Knoppix will abuse the feature and use vt.printk_color=9,9,9,9,11,10,12,
> this is not what serious people would do.

One solution against this and which may satisfy people who are against
this idea, would be to just manipulate the bold and reverse attributes
for errors. On VGA consoles, this would translate into printing in
white instead of grey, and it could also work on ANSI/vt100 terminals.

After all, if the initial intention was to report errors in a more
noticeable way, let's not let the user choose the colors and have
them defined the hard way. It will prevent the salad colors from
appearing.

Willy