From: Ingo Molnar <mingo@elte.hu>
To: Willy Tarreau <w@1wt.eu>
Cc: Rene Herman <rene.herman@keyaccess.nl>,
Oleg Verych <olecom@flower.upol.cz>,
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: "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage"
Date: Sun, 7 Oct 2007 23:11:54 +0200 [thread overview]
Message-ID: <20071007211154.GA27685@elte.hu> (raw)
In-Reply-To: <20071007191309.GS10199@1wt.eu>
* Willy Tarreau <w@1wt.eu> wrote:
> I would say that while I'm not particularly fond of flashy colors
> everywhere, I think that being able to use colors to indicate
> particular actions in progress or conditions can be a good thing. RAID
> errors, devices disabled due to command-line parameters, and general
> anomalies which can cause a hang or panic a few line laters are worth
> coloring. And I don't believe in userland's help here, because for
> that type of messages, the indication should be returned immediately.
> For instance, anyone who has experienced read errors on and IDE disk
> knows that it can literally take hours/days to boot, after displaying
> thousands of messages. Here, having the ability to see that no IRQ was
> assigned or something like this could help.
Exactly. I'm also testing older distros quite regularly with new kernels
and there's it's useful to have an impression of a kernel's output at a
glance. Adding _any_ userspace change (even if i wanted to do it, which
i dont) is out of question. So these are distinct, well-defined usecases
that nobody has brought any coherent argument against yet. VGA isnt
going away anytime soon, certainly not on my testboxes.
Ingo
next prev parent reply other threads:[~2007-10-07 21:12 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 ` [PATCH 0/2] Colored kernel output (run2) Ingo Molnar
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 [this message]
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=20071007211154.GA27685@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 \
--cc=rene.herman@keyaccess.nl \
--cc=w@1wt.eu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.