From: Rene Herman <rene.herman@keyaccess.nl>
To: Willy Tarreau <w@1wt.eu>
Cc: Ingo Molnar <mingo@elte.hu>, 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, 07 Oct 2007 21:53:38 +0200 [thread overview]
Message-ID: <47093942.3090104@keyaccess.nl> (raw)
In-Reply-To: <20071007191309.GS10199@1wt.eu>
On 10/07/2007 09:13 PM, Willy Tarreau wrote:
> On Sun, Oct 07, 2007 at 08:47:52PM +0200, Rene Herman wrote:
>> But well, there actually have been worse arguments given that VGA console
>> is getting less and less important. I recently did a perusal of alternative
>> distributions and didn't find a single one that didn't default to having a
>> splash screen hide the kernel during boot (and if I'm not mistaken, only
>> one of them provided me with the option during installation to not boot
>> into X immediately afterwards).
>
> I don't recall having seen any splash screen on Slackware.
Indeed, but that's the distribution I use and considered switching away
from. Just my luck eh? :-\
> There are two distinct populations :
> - those who are afraid of boot messages and prefer "splash" screens.
> Those people are most common users, grown in non-IT environments. They
> are happy to see a big logo on their BIOS to hide important boot errors,
> and they are the ones who would never have imagined that pressing Escape
> during the boot of windows 3.1/95 provided them with the full text
> messages. Basically, they want to ensure they will never have to worry
> about things they don't understand.
Nor want to understand, often.
> - those who are troubleshooting their system in the early stages (kernel,
> filesystems, network, services, ...). These ones *need* boot messages.
> And there, depending on the hardware, sometimes the FB is better because
> it shows larger lines, sometimes it's worse because the scrollback is
> limited by too low memory.
>
> I personally fit in the second category. And I'm sure most people on this
> list do.
As do I ofcourse. An operating system kernel development list might provide
for a fairly non-average balanced population of "am / am not interested in
the inner workings of computers". Given that most everyone these days uses a
computer, it's still a really small percentage though -- and as evidenced by
the bootsplash thing, even of Linux users (and I've in fact heard real-life
people say they disliked the noisy Linux bootup due to "all those errors").
> I would be miserably sad if I couldn't get my boot messages anymore. It
> already irritates me a lot to loose the ones displayed before switching
> to frame-buffer when a hang happens just afterwards...
Oh quite. I use VGA console myself. But not being able to get to the bootup
messages anymore even for people who do care is not the issue. It's about
finding it a bit hard to get excited about colourization when the "obvious"
way forward is so much more graphically oriented.
As also commented in another reply just now, ways forward also tend to have
their problems but this kind of "innovation" takes me back to the time when
our favorite bulletins board adopted ANSI colours. Today, that seems just a
tad pathetic...
Again, it might not hurt any either, but sheesh.
Rene.
next prev parent reply other threads:[~2007-10-07 19:55 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 ` Rene Herman [this message]
2007-10-07 19:56 ` "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:' usage" 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=47093942.3090104@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 \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox