From: Stefan Reinauer <stepan@suse.de>
To: Robert Morris <rob@r-morris.co.uk>
Cc: Raphael Schmid <Raphael_Schmid@CUBUS.COM>,
"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Bootscreen
Date: Tue, 28 Jan 2003 14:32:52 +0100 [thread overview]
Message-ID: <20030128133252.GC23296@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0301281113480.20283-100000@schubert.rdns.com>
* Robert Morris <rob@r-morris.co.uk> [030128 12:20]:
> There is a very simple reason why Linux shouldn't have a "bootscreen" -
> its a lame idea. We have copied enough of the bad "features" of Windows et
> al into Linux already, IMHO.
Then why not make something better instead of denying it completely.
"It's lame" is not a reason. Seeing the same "Oh, I got my name and
copyright visible in this and that driver" every time I boot a system
is about as lame, and the boot messages are far more a try of a hall of
fame than pure system status in a standardized way. Don't get me wrong,
I don't think it's completely wrong, or should be changed generally.
Rather, Linux has been the operating system of free choice, as long as
I can think of it. And this free choice might also mean that people want
some graphics surrounding their boot messages or replace them.
> FWIW, I usually remove the graphics from LILO/GRUB config as installed by
> default these days.
Which is your perfect right, if you like it that way. But there are
people who think different. Don't call them lame.
> Most of the machines I maintain are very seldom rebooted, but if someone
> was to do a reboot, I would want them to be able to observe any errors or
> other abnormal output from the boot-up process.
A graphical boot does not necessarily hide all kernel messages. Look
at my bootsplash patches how to do it in a technical sane way.
ftp.suse.com/pub/people/stepan/bootsplash/. If you have an embedded
device with a fixed system and non-variable hardware you just don't need
the information from the kernel messages.
> A "bootscreen" makes it
> more likely that such an error message would be more likely to go
> unnoticed - and, if they became commonplace, may eventually result in
> developers making the on-boot output less verbose/informative/etc, on the
> basis that it isn't likely to be seen in the first place!
Make it configurable, so that everybody can turn it on and off, and
don't turn it on by default. This is done with the fbcon stuff anyways,
which is mandatory for a splash screen. Where's the problem in just not
switching such a function on?
> The stuff you see on your screen when your Linux installation boots up
> weren't put there for no reason. Please lets leave them there!
There's always a reason for someone. This does not mean that it's my
reason, too. Microsoft have their reasons as well with their backdoor
politics...
Stefan
--
The use of COBOL cripples the mind; its teaching should, therefore, be
regarded as a criminal offense. -- E. W. Dijkstra
next prev parent reply other threads:[~2003-01-28 13:23 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 9:01 Bootscreen Raphael Schmid
2003-01-28 9:52 ` Bootscreen John Bradford
2003-01-28 10:49 ` Bootscreen DervishD
2003-01-28 11:20 ` Bootscreen Robert Morris
2003-01-28 11:44 ` Bootscreen John Bradford
2003-01-28 11:48 ` Bootscreen Wichert Akkerman
2003-01-28 12:15 ` Bootscreen Robert Morris
2003-01-28 12:55 ` Bootscreen Alan Cox
2003-01-28 13:09 ` Bootscreen Wichert Akkerman
2003-01-28 13:47 ` Bootscreen Alan Cox
2003-01-28 14:06 ` Bootscreen John Bradford
2003-01-28 14:14 ` Bootscreen Richard B. Tilley (Brad)
2003-01-28 14:33 ` Bootscreen Robert Morris
2003-01-28 14:32 ` Bootscreen Wichert Akkerman
2003-01-28 14:45 ` Bootscreen Jos Hulzink
2003-01-28 14:47 ` Bootscreen Wichert Akkerman
2003-01-28 14:57 ` Bootscreen Richard B. Tilley (Brad)
2003-01-28 14:58 ` Bootscreen Wichert Akkerman
2003-01-28 15:07 ` Bootscreen Richard B. Tilley (Brad)
2003-01-28 15:14 ` Bootscreen Wichert Akkerman
2003-01-28 15:20 ` Bootscreen Richard B. Tilley (Brad)
2003-01-28 15:25 ` Bootscreen Wichert Akkerman
2003-01-29 10:19 ` Bootscreen Horst von Brand
2003-01-28 15:05 ` Bootscreen Alan Cox
2003-01-28 15:06 ` Bootscreen John Bradford
2003-01-29 9:57 ` Module security [Was: Re: Bootscreen] Horst von Brand
2003-01-28 14:53 ` Bootscreen Oliver Neukum
2003-01-28 13:22 ` Bootscreen Jos Hulzink
2003-01-28 14:35 ` Bootscreen Rogier Wolff
2003-01-28 12:08 ` Bootscreen Robert Morris
2003-01-28 12:17 ` Bootscreen John Bradford
2003-01-28 14:15 ` Bootscreen Roy Sigurd Karlsbakk
2003-01-28 18:46 ` Bootscreen H. Peter Anvin
2003-01-29 9:13 ` Bootscreen Horst von Brand
2003-01-29 9:35 ` Bootscreen Xavier Bestel
2003-01-29 13:19 ` Bootscreen Roy Sigurd Karlsbakk
2003-01-28 13:32 ` Stefan Reinauer [this message]
2003-01-28 13:46 ` Bootscreen Robert Morris
2003-01-28 14:38 ` Bootscreen Stefan Reinauer
2003-01-28 13:52 ` Bootscreen Roy Sigurd Karlsbakk
2003-01-29 8:06 ` Bootscreen Zwane Mwaikambo
2003-01-29 13:17 ` Bootscreen Roy Sigurd Karlsbakk
2003-01-29 15:48 ` Bootscreen Zwane Mwaikambo
2003-01-28 13:55 ` Bootscreen John Bradford
2003-01-28 14:28 ` Bootscreen Wichert Akkerman
2003-01-28 14:43 ` Bootscreen John Bradford
2003-01-28 14:45 ` Bootscreen Wichert Akkerman
2003-01-28 17:15 ` Bootscreen Valdis.Kletnieks
2003-01-28 12:10 ` Bootscreen Stefan Reinauer
2003-01-28 14:50 ` Bootscreen Alan Cox
2003-01-28 15:07 ` Bootscreen Stefan Reinauer
2003-01-28 15:09 ` Bootscreen John Bradford
2003-01-28 17:41 ` Bootscreen Erik Mouw
2003-01-28 20:11 ` Bootscreen Arador
2003-01-28 21:13 ` Bootscreen Bernd Eckenfels
2003-01-28 17:48 ` Bootscreen Martin J. Bligh
2003-01-28 19:24 ` Bootscreen Ingo Oeser
2003-01-28 18:13 ` Bootscreen Aaron Lehmann
2003-01-28 18:21 ` Bootscreen Prasad
-- strict thread matches above, loose matches on Subject: below --
2003-01-28 10:33 AW: AW: Bootscreen Raphael Schmid
2003-01-28 10:52 ` John Bradford
2003-01-28 13:16 ` Bootscreen Stefan Reinauer
[not found] <398E93A81CC5D311901600A0C9F29289469376@cubuss2>
2003-01-28 11:05 ` Bootscreen Alex Riesen
2003-01-28 11:38 ` Bootscreen Jos Hulzink
2003-01-28 13:13 Bootscreen Raphael Schmid
2003-01-28 14:35 ` Bootscreen Xavier Bestel
2003-01-30 7:25 ` Bootscreen Pavel Machek
2003-01-31 17:40 ` Bootscreen Jörn Engel
2003-01-31 17:45 ` Bootscreen Pavel Machek
2003-01-28 14:11 AW: Bootscreen Raphael Schmid
2003-01-28 14:26 ` John Bradford
2003-01-28 14:48 ` Bootscreen Stefan Reinauer
2003-01-28 14:29 ` AW: Bootscreen Robert Morris
2003-01-28 14:59 ` Bootscreen Stefan Reinauer
2003-01-28 14:34 ` Bootscreen jeff millar
2003-01-28 14:40 ` Bootscreen John Bradford
2003-01-28 16:41 ` Bootscreen Valdis.Kletnieks
2003-01-28 21:48 Bootscreen Balram Adlakha
2003-01-28 21:59 ` Bootscreen John Bradford
2003-01-29 14:46 ` Bootscreen Denis Vlasenko
2003-01-29 19:52 ` Bootscreen Balram Adlakha
2003-01-30 6:53 ` Bootscreen Denis Vlasenko
2003-01-30 10:18 ` Bootscreen Bernd Eckenfels
2003-01-30 10:39 ` Bootscreen Helge Hafting
2003-01-30 13:54 ` Bootscreen Stefan Reinauer
2003-01-29 15:09 ` Bootscreen Horst von Brand
2003-01-29 8:30 Bootscreen Raphael Schmid
2003-01-29 8:35 Bootscreen Raphael Schmid
2003-01-29 17:53 ` Bootscreen Arador
2003-01-29 13:59 Bootscreen Raphael Schmid
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=20030128133252.GC23296@suse.de \
--to=stepan@suse.de \
--cc=Raphael_Schmid@CUBUS.COM \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@r-morris.co.uk \
/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