From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Bootscreen [had to throw in 2 cents worth, sorry]
Date: Wed, 29 Jan 2003 17:31:04 +0100 [thread overview]
Message-ID: <20030129163104.GV30184@lug-owl.de> (raw)
In-Reply-To: <1043854259.877.25.camel@RobsPC.RobertWilkens.com>
[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]
On Wed, 2003-01-29 10:31:00 -0500, Rob Wilkens <robw@optonline.net>
wrote in message <1043854259.877.25.camel@RobsPC.RobertWilkens.com>:
> On Wed, 2003-01-29 at 09:46, Denis Vlasenko wrote:
> > Yeah, dude, let's dumb down our users... don't allow them
> > to become curious and start learning.
>
> As I recall, the way Windows 95/98/ME operated with the bootscreen (and
> this might be wise for Linux as well) is to display a bootscreen, but
> have it disappear if someone taps the escape key and returned to the
> console where they CAN OPTIONALLY read the messages if their heart
> desires. In Windows 2000/XP, this is no longer, sadly, how it works,
> but there still was (I believe) a mode in that OS where it displays all
> the boot messages (/SOS option or similar).
Well, what do you do (think 2.5.x) when you don't have keyboard drivers
compiled in? I currently do use them as loaded modules, *if* at all I do
need them. Most of the time, my alphas only have two (or three) cables
plugged in: power, network and possibly serial console... If there's a
monitor, it's wired to a monitor switch (so you can see the messages,
but basically, since there's no keyboard support loaded, it's useless),
but it won't be used. Serial console is my way to go...
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur
fuer einen Freien Staat voll Freier Bürger" | im Internet!
Shell Script APT-Proxy: http://lug-owl.de/~jbglaw/software/ap2/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-29 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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 15:31 ` Bootscreen [had to throw in 2 cents worth, sorry] Rob Wilkens
2003-01-29 16:31 ` Jan-Benedict Glaw [this message]
2003-01-29 16:52 ` Bootscreen [had to throw in 0.2 " Herman Oosthuysen
2003-01-29 19:45 ` LKML I/O scheduling (was Re: Bootscreen [had to throw in 2 cents worth, sorry]) Alex Bligh - linux-kernel
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
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=20030129163104.GV30184@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox