[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <47096752.2070107@keyaccess.nl>
Date: Mon, 08 Oct 2007 01:10:10 +0200
From: Rene Herman <rene.herman@...access.nl>
To: Alistair John Strachan <alistair@...zero.co.uk>
CC: Willy Tarreau <w@....eu>, Ingo Molnar <mingo@...e.hu>,
Oleg Verych <olecom@...wer.upol.cz>,
Jan Engelhardt <jengelh@...putergmbh.de>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Dave Jones <davej@...hat.com>,
Krzysztof Halasa <khc@...waw.pl>,
Medve Emilian-EMMEDVE1 <Emilian.Medve@...escale.com>,
Helge Deller <deller@....de>
Subject: Re: "Re: [PATCH 0/2] Colored kernel output (run2)" + "`Subject:'
usage"
On 10/08/2007 12:40 AM, Alistair John Strachan wrote:
> Splash screens are clearly cosmetic, and it's kind of shameful (imo) that
> important messages explaining real problems are obscured from view by
> functionless splash screens.
They're not functionless. You (and I) might not care for the function, but
their function is providing a "slick" bootup. That's why so many if not
basically all distributions of recent origin use them. Go ask Ubuntu for
example.
> Personally, I think muddying the vga colour argument with splash screen stuff
> is bogus, they're very functionally separable ideas. A coloured oops seems to
> be a good way of telling novice users what information is relevant to their
> bug report.
But when they're hidden by a splash screen, you don't see them any better
when they're red than when they're white. Splash screens were not mentioned
as any sort of alternative, their prevalence was mentioned as indication
that VGA console is only ever getting less important.
I find Alan's suggestion to provide the functionality the same way you'd
provide for translated kernel messages (seeing as how there also are people
that want those) much more sensible.
Rene.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists