From: "Rafael E. Herrera" <raffo@cdi.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Animated framebuffer logo for 2.4.1
Date: Tue, 13 Feb 2001 02:11:10 -0500 [thread overview]
Message-ID: <3A88DE0E.42EE74F5@cdi.com> (raw)
In-Reply-To: <20010201183231.A373@tuxia.com> <l03130323b6ae7005d490@[192.168.239.101]>
> Not good enough in isolation. Suppose the kernel freezes at a very early
> stage, such as while detecting the CPU(s) or PCI bridge - are your geeky
> reaction times fast enough to dismiss the logo in time to see the relevant
> messages? I agree with others that this should be a boot option - and not
...
> Eg: in lilo.conf use append = "bootlogo" to turn the logo on (it should
> always be off by default, but can be turned on by distro makers or
> end-users) - but then if you type "linux nologo" at the LILO prompt, the
> "nologo" should over-ride the "bootlogo" so there's always a way to see all
> the messages.
In a PC and if using lilo, you always get a lilo prompt (if so
configured) after the initial power on tests. Passing a "nologo" option
to lilo would seem a reasonable way to turn the feature off. The same
could apply to othe boot loaders and other archs. By the way, suse 7.1
has a graphical boot, no animation though, just a big penguin; some
hacked lilo version, maybe?
--
Rafael
next prev parent reply other threads:[~2001-02-13 7:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 17:32 [ANNOUNCE] Animated framebuffer logo for 2.4.1 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-09 9:21 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
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=3A88DE0E.42EE74F5@cdi.com \
--to=raffo@cdi.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.