From: Bill Davidsen <davidsen@tmr.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Jones <davej@redhat.com>
Subject: Re: [PATCH] Cute feature: colored printk output
Date: Sat, 06 Oct 2007 20:50:05 -0400 [thread overview]
Message-ID: <47082D3D.5090101@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710062158190.20637@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Oct 6 2007 15:53, Bill Davidsen wrote:
>> Jan Engelhardt wrote:
>>> Colored kernel message output
>>>
>>> Let's work more on Linux's cuteness! [http://lkml.org/lkml/2007/10/4/431]
>>> The following patch makes it possible to give kernel messages a
>>> selectable color which helps to distinguish it from other noise,
>>> such as boot messages. NetBSD has it, OpenBSD has it, FreeBSD to some
>>> extent, so I think Linux should too.
>>>
>>> Inspired by cko (http://freshmeat.net/p/cko/), but independently
>>> written, later contributed forth and back.
>>>
>> I like it, although having a boot option would be nice (I have a friend with
>> color perception issues).
>
> sysfs attributes can be set at boot time (and not only that).
> Here, try the "davej's salad" configuration :-)
>
> vt.default_red=0,192,128,170,0,170
> vt.default_grn=0,0,170,128,64,0
> vt.default_blu=0,0,0,0,128,128
> vt.printk_color=1,1,1,1,5,3,2
>
>> I start my root xterm in white on blue for identification, so color coding
>> sounds like a great idea to me.
>
> This has nothing to do with xterms, this is "VGA color console" only.
> xterm config is in /usr/share/X11/app-defaults/XTerm-color.
Try reparsing that... I said I use color coding in root xterm, so I am
generally in favor of the color coding concept to make important
messages obvious. Is that clearer?
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2007-10-07 0:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 19:13 [PATCH] Cute feature: colored printk output Jan Engelhardt
2007-10-05 19:19 ` Lennart Sorensen
2007-10-05 19:21 ` Jan Engelhardt
2007-10-05 19:24 ` Lennart Sorensen
2007-10-05 19:32 ` Jan Engelhardt
2007-10-05 19:43 ` Lennart Sorensen
2007-10-05 19:55 ` Jan Engelhardt
2007-10-05 20:23 ` Medve Emilian-EMMEDVE1
2007-10-05 23:22 ` Krzysztof Halasa
2007-10-05 23:47 ` Jan Engelhardt
2007-10-06 0:10 ` Krzysztof Halasa
2007-10-06 0:23 ` Jan Engelhardt
2007-10-06 0:26 ` Jan Engelhardt
2007-10-06 11:58 ` Krzysztof Halasa
2007-10-06 11:08 ` Ingo Molnar
2007-10-06 17:16 ` Dave Jones
2007-10-06 18:09 ` Oleg Verych
2007-10-06 19:53 ` Bill Davidsen
2007-10-06 20:01 ` Jan Engelhardt
2007-10-07 0:50 ` Bill Davidsen [this message]
2007-10-07 8:42 ` Jan Engelhardt
2007-10-06 21:19 ` Miguel Botón
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=47082D3D.5090101@tmr.com \
--to=davidsen@tmr.com \
--cc=davej@redhat.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
/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