public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alistair John Strachan <alistair@devzero.co.uk>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Willy Tarreau <w@1wt.eu>, 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: Mon, 8 Oct 2007 00:20:59 +0100	[thread overview]
Message-ID: <200710080020.59742.alistair@devzero.co.uk> (raw)
In-Reply-To: <47096752.2070107@keyaccess.nl>

On Monday 08 October 2007 00:10:10 Rene Herman wrote:
> 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.

Obviously true, but that's not a reason to bar enhancements to the VGA 
console. Right now, there's no sane way to have a splash screen in userspace 
handle an oops, so people looking to reproduce and detect the root of a 
problem will inevitably fall back to VGA (or vesa, presumably), where colour 
might be useful.

I recall seeing a distro kernel oops early in boot, where the palette had been 
corrupted by the splash so the oops wasn't readable. That's bad, right?

Don't get me wrong, I don't care for the feature much, I just don't 
think "splash screens are defacto" is a reason to shy away from a feature 
that could be useful for novices reporting kernel bugs. These people are 
probably inbetween those that must have a shiny splash and those that fix the 
kernel bugs.

Of course, what Alan said elsewhere about breaking things that work is a good 
reason to not add the feature, or at least make it only happen on a real 
display.

-- 
Cheers,
Alistair.

137/1 Warrender Park Road, Edinburgh, UK.

  reply	other threads:[~2007-10-07 23:21 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
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 [this message]
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=200710080020.59742.alistair@devzero.co.uk \
    --to=alistair@devzero.co.uk \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox