From: Ingo Molnar <mingo@elte.hu>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>, Krzysztof Halasa <khc@pm.waw.pl>,
Medve Emilian-EMMEDVE1 <Emilian.Medve@freescale.com>,
Helge Deller <deller@gmx.de>
Subject: Re: [PATCH 0/2] Colored kernel output (run2)
Date: Sun, 7 Oct 2007 08:07:07 +0200 [thread overview]
Message-ID: <20071007060706.GA18768@elte.hu> (raw)
In-Reply-To: <20071006210349.GG22435@flower.upol.cz>
* Oleg Verych <olecom@flower.upol.cz> wrote:
> > > * completely useless, if properly implemented in userspace (with
> > > much reacher functionality).
> >
> > that's hogwash. No user-space runs during early bootup. (and yes i
> > want a color code at glance if something hangs in early bootup)
> > Nothing will color-code crashes, etc., etc. Control of the _kernel_
> > console by user-space is complete nonsense.
>
> If it is so important for major kernel developer like you, Ingo, then
> why there's no scrollback at first place? Why nothing like that was
> not implemented up until now?
even if it were true (which it isnt), that is not an argument against
including a useful change that exists now and that people are interested
in. (and yes, i have implemented kernel console improvements in the past
and vga scrollback support was in fact amongst one of my first ever
Linux kernel hacks so your comment is doubly wrong.)
> My first ever Linux hack was changing default console output color. I
> think it was seven years ago. I though, it was not serious, if nobody
> did that already (in the 2.2.14).
>
> Please, don't mix important stuff here. I know, what kernel console
> is.
your arguments are not an answer to my technical points, which i'll
repeat here:
| | [...] No user-space runs during early bootup. (and yes i want a
| | color code at glance if something hangs in early bootup) Nothing
| | will color-code crashes, etc., etc. Control of the _kernel_ console
| | by user-space is complete nonsense.
today's console code development goes in exactly the opposite direction:
we are including (formerly-) user-space console functionality in the
kernel so that we can for example print oopses even if we are in X mode.
> > this is nice and robust functionality that i personally welcome. The
> > default is not changed in any way.
> >
> > (btw., i corrected the subject line to remove the 'NAK'. Why do you
> > think you can 'NAK' a patch in this field?)
>
> I added comment (like this), so anyone can skip reading body, if
> headers are "Oleg Verych && NAK". In case if `NAK' have a magic
> meaning in the LKML, like control characters in the tty, i'm sorry.
yes, a 'NAK' has a particular meaning on lkml.
> But how to express opinion quickly and easily?
by writing a quick email expressing your opinion and waiting to see the
discussion play out itself ...
but it is very rude to 'NAK' a patch and it should only be done
carefully.
Ingo
next prev parent reply other threads:[~2007-10-07 6:07 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0710062005190.5969@fbirervta.pbzchgretzou.qr>
2007-10-06 19:13 ` [PATCH 1/2] Colored kernel output (run2) Jan Engelhardt
2007-10-08 13:28 ` Denys Vlasenko
2007-10-06 19:13 ` [PATCH 2/2] " Jan Engelhardt
[not found] ` <20071006195105.GE22435@flower.upol.cz>
[not found] ` <20071006194820.GA30579@elte.hu>
2007-10-06 21:03 ` [PATCH 0/2] " Oleg Verych
2007-10-06 21:03 ` Jan Engelhardt
2007-10-06 21:55 ` About summary in the subject (Re: [PATCH 0/2] Colored kernel output (run2)) Oleg Verych
2007-10-07 6:07 ` Ingo Molnar [this message]
2007-10-07 11:10 ` "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage" Oleg Verych
2007-10-07 14:15 ` NAK nettiquete (was Re: "Re: [PATCH 0/2] Colored kernel output (run2)" Valdis.Kletnieks
2007-10-07 15:12 ` Alan Cox
2007-10-07 15:29 ` Jan Engelhardt
2007-10-07 16:23 ` Alan Cox
2007-10-07 23:09 ` Jan Engelhardt
2007-10-07 15:46 ` Valdis.Kletnieks
2007-10-07 18:11 ` NAK nettiquete (was " Arnaldo Carvalho de Melo
2007-10-07 16:12 ` "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage" Ingo Molnar
2007-10-07 18:47 ` Rene Herman
2007-10-07 18:58 ` Jan Engelhardt
2007-10-07 19:27 ` Rene Herman
2007-10-07 20:02 ` Jan Engelhardt
2007-10-07 19:13 ` Willy Tarreau
2007-10-07 19:47 ` Oleg Verych
2007-10-07 21:23 ` Ingo Molnar
2007-10-07 21:38 ` Alan Cox
2007-10-12 13:42 ` Bill Davidsen
2007-10-08 3:23 ` Willy Tarreau
2007-10-08 19:27 ` initramfs: coloring in userspace, "[PATCH 0/2] Colored kernel output (run2)" Oleg Verych
2007-10-07 19:53 ` "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage" Rene Herman
2007-10-07 19:56 ` Jan Engelhardt
2007-10-07 20:00 ` Rene Herman
2007-10-07 20:04 ` Jan Engelhardt
2007-10-07 20:06 ` Rene Herman
2007-10-07 20:50 ` tty UI (Re: [PATCH 0/2] Colored kernel output (run2)) Oleg Verych
2007-10-07 20:43 ` Jan Engelhardt
2007-10-07 22:18 ` syntax highlighting, emacs ([PATCH " Oleg Verych
2007-10-07 22:11 ` Jan Engelhardt
2007-10-08 0:29 ` Ken Moffat
2007-10-08 3:29 ` "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage" Willy Tarreau
2007-10-07 21:11 ` Ingo Molnar
2007-10-07 23:02 ` Oleg Verych
2007-10-07 23:01 ` Jan Engelhardt
2007-10-07 23:33 ` Oleg Verych
2007-10-07 22:40 ` Alistair John Strachan
2007-10-07 23:10 ` Rene Herman
2007-10-07 23:20 ` Alistair John Strachan
2007-10-07 23:33 ` Alistair John Strachan
2007-10-07 23:15 ` Alan Cox
2007-10-07 16:37 ` Jan Engelhardt
2007-10-12 13:16 ` Bill Davidsen
2007-10-12 14:57 ` Oleg Verych
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071007060706.GA18768@elte.hu \
--to=mingo@elte.hu \
--cc=Emilian.Medve@freescale.com \
--cc=davej@redhat.com \
--cc=deller@gmx.de \
--cc=jengelh@computergmbh.de \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=olecom@flower.upol.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox