Re: NAK nettiquete (was Re: "Re: [PATCH 0/2] Colored kernel output (run2)"

[Alan Cox <alan@lxorguk.ukuu.org.uk>]

> The few times I've tried to NAK something outright, I've always tried to attach
> plenty of technical explanation 

Fair comment to my "silly" response

The problems I see are

- We run on a lot more than VGA PC consoles
- We have serial consoles (which may or may not be VT132/ANSI compliant)
- The printk paths are run at IRQ time ASAP to get messages to console,
that could mean we split existing colour escape code processing and the
like.
- People redirect the console feed other places via ioctl. Some of them
parse "<%d>" as the start

But most importantly:

- If you want to do "pretty" boot up you do it in X or frame buffer
(which is going to get easier and easier with the X shift to kernel side
video support)
- If you want to do a coloured display after boot then this is a matter
for your logging tools

As with translation the kernel is the wrong place to do this work.

What I would much rather people thought about was

- Marker modes for translation (so you know which bits of a message are
formatted up)
- More consistency on the use of "name: blah" to make it easier to parse
- Turning more messages from kernel logs to events when it makes sense
(eg "Disk Full", "Media Error", "CPU on fire")

So if you want to do a pretty boot, then solve the big picture, the
framebuffer initrd graphical boot, the boot display, the combining of
artwork and messages in user space from initrd run code.

'leet kernel messages in flashing red are not really the problem that
needs solving to do this.

Alan