public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Reinauer <stepan@suse.de>
To: John Bradford <john@grabjohn.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bootscreen suggestions that don't involve kernel modifications
Date: Thu, 30 Jan 2003 15:13:08 +0100	[thread overview]
Message-ID: <20030130141308.GD6066@suse.de> (raw)
In-Reply-To: <200301291348.h0TDmHfu001672@darkstar.example.net>

* John Bradford <john@grabjohn.com> [030129 14:48]:
> I don't think it is appropriate to include graphical boot screen
> capabilities in the kernel.  There are better ways to achieve what you
> want to do:
> 
> * Verbose start-up messages on the console
> Leave things how they are

agreed 

> * No start up messages on the console
> Either use the quiet option, or re-direct the output to serial console
> or another virtual terminal.

> * Graphical boot screen
> Do not have the VGA card configured as a console device at all.  Set
> the console output to a serial port for debugging, if necessary.  Have
> the bootloader configure the VGA card, and display the graphic.  Boot
> in to X, and let X re-configure the VGA card at startup.

Some method to switch between verbose and non-verbose mode on the screen
interactively would be useful and it should not loose old messages. Not
have vga configured as console device kind of gives you a hard time
here. My bootsplash patch takes care of this by only "hiding" the text
instead of not redirect it to vga, so the text buffers are valid all the
time and visible as soon as you switch them on

Stefan
  
-- 
The use of COBOL cripples the mind; its teaching should, therefore, be
regarded as a criminal offense.                      -- E. W. Dijkstra

      reply	other threads:[~2003-01-30 14:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 13:25 Scaring the non-geeks (was Bootscreen) Raphael Schmid
2003-01-29 13:48 ` Bootscreen suggestions that don't involve kernel modifications John Bradford
2003-01-30 14:13   ` Stefan Reinauer [this message]

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=20030130141308.GD6066@suse.de \
    --to=stepan@suse.de \
    --cc=john@grabjohn.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox