From: Rene Herman <rene.herman@keyaccess.nl>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Ingo Molnar <mingo@elte.hu>, Oleg Verych <olecom@flower.upol.cz>,
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, 07 Oct 2007 21:27:30 +0200 [thread overview]
Message-ID: <47093322.1030200@keyaccess.nl> (raw)
In-Reply-To: <Pine.LNX.4.64.0710072053300.16301@fbirervta.pbzchgretzou.qr>
On 10/07/2007 08:58 PM, Jan Engelhardt wrote:
> On Oct 7 2007 20:47, Rene Herman wrote:
>>>> Coloring isn't useful. If it was, it would be implemented ~16 years
>>>> ago.
>>> Congratulations, this is the most stupid argument i've ever read on lkml.
>> "Ay. World is finished. Everyone can go home and watch Friends reruns now."
>>
>> But well, there actually have been worse arguments given that VGA console is
>> getting less and less important.
>> [...]
>> Sure, that in itself needn't necesarily be of concern to anyone who,
>> err, is not concerned but any such colouring feature appearing when
>> there's only a smathering of people left that still cares about the VGA
>> console in the first place really isn't all _that_ far out as an
>> argument...
>
> In case you have not noticed, the coloring also applies to FB. As far as
> I can oversee, it's only "missing" for serial and PROMs.
Must say I did concentrate on VGA, but the [...] bit in the quote above was
about how everything I encountered put up a bootsplash hiding _everything_
and about booting into X immediately, not about FB...
I saw you remark on FB console in a reply to Alan just now and I quite agree
with you. The (current) FB console is slow and I'll add "dumb" myself. When
you have a 1280x1024 screen available, you get to do cool things like put up
nice little windows and exclamation mark icons on errors, not just pretend
you're really 132x50 (or whatever).
Alan's sketched more generic markup/unification would be The Way Forward it
seems. Given that TWF is mostly defined as "That Which Is Not" (and how it
seems to have a tendency to defend that status vigorously) telling me/us to
shelve that objection for 10 years might be okay -- but generally I'm having
a fairly hard time getting excited about printk colourizing.
Rene.
next prev parent reply other threads:[~2007-10-07 19:28 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 [this message]
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=47093322.1030200@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--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=mingo@elte.hu \
--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