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

[Jan Engelhardt]

On Oct 8 2007 01:02, Oleg Verych wrote:
>
>If you are not going to see OOPes of new kernels running old distros, ask
>any perl hacker (as they lovely mentioned in lkml) to hack for you
>something like:
>
>sed -u -e '
>/^<1/s_^_'$COLOR1'_
>/^<2/s_^_'$COLOR2'_
>/^<3/s_^_'$COLOR3'_
>/^<4/s_^_'$COLOR4'_
>/^<5/s_^_'$COLOR5'_
>/^<6/s_^_'$COLOR6'_
>/^<7/s_^_'$COLOR7'_
>' < /proc/kmsg >/dev/tty
>
>place whole that perl shit on initrams of your kernel, run it in
>background as early as possible with switched off default console output
>(i.e. quiet boot).
>
>OVER.

Speaking of over, this does not fly at all. If you call panic(),
for whatever reason you want, then the printk() is the last thing
that happens after that, you can declare userspace dead.
On oopses, it depends on their severity. Eventually procfs goes
whoops and the kmsg transmission mechanism does not work, and oh,
userspace can't help it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/