public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: Pavel Machek <pavel@suse.cz>
Cc: Helge Hafting <helgehaf@idb.hist.no>, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Animated framebuffer logo for 2.4.1
Date: Mon, 12 Feb 2001 14:00:31 -0800	[thread overview]
Message-ID: <3A885CFF.2010109@megapathdsl.net> (raw)
In-Reply-To: <3A83B6B0.8261F3CF@idb.hist.no> <3A83C4A1.5090903@megapathdsl.net> <20010211234718.K3748@bug.ucw.cz>

Pavel Machek wrote:

> Hi!
> 
> 
>> Right.  Add the option.  Default to "spew mode",
>> but make it easy for distributions to show people
>> a non-threatening boot process.  
> 
> Wrong.

We're talking about an _option_.  In fact, it could 
be set up as a boot time parameter.  Then, if a boot
process gets wedged, the user can just reboot with
the option disabled.

I really don't understand why this is such a hot
button for some people.  I repeat "option."

>> Since, as Christophe mentions, the boot messages would
>> still be accessible via CTRL-ALT-F2, I don't see what 
>> the problem is with at least making this an option.
> 
> If your system crashes hard, you have only graphical logo to stare
> at. Any warning messages are hidden. Not good.

Again.  Boot parameter.

	Miles

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://vger.kernel.org/lkml/

  parent reply	other threads:[~2001-02-12 21:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-09  9:21 [ANNOUNCE] Animated framebuffer logo for 2.4.1 Helge Hafting
2001-02-09  9:32 ` David Lang
2001-02-09 10:21 ` Miles Lane
2001-02-09 11:36   ` Werner Almesberger
2001-02-09 11:47     ` Miles Lane
2001-02-09 12:28       ` Werner Almesberger
2001-02-10  3:50     ` Nick Papadonis
2001-02-09 16:40   ` Mike Porter
2001-02-11 22:47   ` Pavel Machek
2001-02-12 17:18     ` Peter Kundrat
2001-02-12 22:00     ` Miles Lane [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-02-01 17:32 Juergen Schneider
2001-02-07 23:40 ` Pavel Machek
2001-02-08 12:37   ` Mike A. Harris
     [not found]     ` <Pine.LNX.4.33.0102080736190.5431-100000@as df.capslock.lan>
2001-02-08 14:08       ` christophe barbe
2001-02-08 18:42         ` Miles Lane
2001-02-09  7:03         ` Mike Galbraith
     [not found]           ` <Pine.Linu.4.10.10102090732320.1612-100000@ mikeg.weiden.de>
2001-02-09  8:12             ` christophe barbe
2001-02-09  9:45               ` Mike Galbraith
2001-02-12 11:00                 ` Adrian Cox
2001-02-11 14:07     ` Werner Almesberger
2001-02-12 15:23 ` Martin Laberge
2001-02-12 22:31   ` Miles Lane
2001-02-13  3:46 ` Rafael E. Herrera
2001-02-13  5:10 ` Jonathan Morton
2001-02-13  7:11   ` Rafael E. Herrera

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=3A885CFF.2010109@megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=helgehaf@idb.hist.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.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