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

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Ingo Molnar <mingo@...>
Cc: Jan Engelhardt <jengelh@...>, Linux Kernel Mailing List <linux-kernel@...>, Dave Jones <davej@...>, Krzysztof Halasa <khc@...>, Medve Emilian-EMMEDVE1 <Emilian.Medve@...>, Helge Deller <deller@...>
Date: Sunday, October 7, 2007 - 7:10 am

Hallo, Ingo.

On Sun, Oct 07, 2007 at 08:07:07AM +0200, Ingo Molnar wrote:

To clarify. `Scrollback' here is *useful* scrollback during early boot
and OOPs (which is absent, AFAIK), "nothing like that" is coloring of the
messages by loglevel.


Coloring isn't useful. If it was, it would be implemented ~16 years ago.


This `scrollback' is usual late boot / console one. If fact useful,
until first tty switch or if `screen` cannot be used. But for some
reason if scrolling region (DECSTBM) is less than whole screen, nothing
works. And if width set to odd number of columns

`stty columns $((80-1))`

whole output becomes somewhat funny.


The kernel developer talks about what is important to him. This is not
technical point.


Because without userspace kernel panics. And if something is broken very
early, then time to do kernel development better (not to break working
early booting stuff for everybody), rather than to talk about importance
of the color. I think, same applies to kernel debugger, that still
is not in mainline (AFAIK).


Not control, but flexible coloring (any kind of highlighting), selecting
of useful information, i.e. making output more user friendly. This are
things, which all *users* (not developers) expect in boot process of the
one's _machine_, as opposed to debugging (early boot) kernel bugs.


I'm not sure what kind of printing it is. I do not use X much, but when i
did, i recall MCE messages in xterm, when over-clocked CPU was going
crazy, though.


But what about (NAK && ! any_important_kernel_developer_name)?


Quick is not for me (i did accepted "config NO" size reduction review,
btw), but for those, who reads LKML or looks on archive search results.

I just am amazed how `Subject' is miss-used. I personally like to have
most of the interesting information gathered from all that thousands of
(not only LKML) messages. But a thread with all-like-one subjects,
subjects that for some reason are taking place on the screen of
MUAs (empty space if they are the same). Thus, short (easy to get right)
summary in subject is more that welcome by me.


That was a review of the implementation, an opinion on whole idea. Idea
of yet another ugly kernel functionality, just because *BSD kernels have
one.

I like highlighting, i like to make it very flexible, nice and
interesting[0]. This is possible only in the userspace, right after first
process ran from initramfs. This happens very quickly usually. And yes,
this is not acceptable/available for kernel developers/maintainers.

[0] not much, but something <ftp://flower.upol.cz/upload/debian.sh> 

____
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH 0/2] Colored kernel output (run2), Oleg Verych, (Sat Oct 6, 5:03 pm)
Re: [PATCH 0/2] Colored kernel output (run2), Ingo Molnar, (Sun Oct 7, 2:07 am)
"Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:'..., Oleg Verych, (Sun Oct 7, 7:10 am)
Re: "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subje..., Alistair John Strachan, (Sun Oct 7, 6:40 pm)
Re: "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subje..., Alistair John Strachan, (Sun Oct 7, 7:33 pm)
Re: "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subje..., Alistair John Strachan, (Sun Oct 7, 7:20 pm)
Re: tty UI (Re: [PATCH 0/2] Colored kernel output (run2)), Jan Engelhardt, (Sun Oct 7, 4:43 pm)
Re: NAK nettiquete (was Re: "Re: [PATCH 0/2] Colored kernel ..., Arnaldo Carvalho de Melo, (Sun Oct 7, 2:11 pm)
Re: [PATCH 0/2] Colored kernel output (run2), Jan Engelhardt, (Sat Oct 6, 5:03 pm)