From owner-freebsd-hackers  Sat Feb 15 19:38:56 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id TAA09905
          for hackers-outgoing; Sat, 15 Feb 1997 19:38:56 -0800 (PST)
Received: from lightside.com (hamby1.lightside.net [207.67.176.17])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id TAA09900
          for <hackers@freebsd.org>; Sat, 15 Feb 1997 19:38:53 -0800 (PST)
Received: by lightside.com (SMI-8.6/SMI-SVR4)
	id TAA05806; Sat, 15 Feb 1997 19:38:35 -0800
Date: Sat, 15 Feb 1997 19:38:35 -0800
From: jehamby@lightside.com (Jake Hamby)
Message-Id: <199702160338.TAA05806@lightside.com>
To: jehamby@lightside.com, jfieber@indiana.edu
Subject: Re: boot messages (was: Sun Workshop compiler vs. GCC?)
Cc: hackers@freebsd.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-MD5: HAOkGltzm/PeYOudgRJA9Q==
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

John Fieber writes:

> On Sat, 15 Feb 1997, Jake Hamby wrote:
> 
> > I also suggest that FreeBSD add a splash screen with clearly printed 
> > directions on how to bypass it to see the hardware probes underneath.
> 
> The windows 95 splash screen disappears at the press of Escape,
> revealing whatever is going on on the console (not much usually). 
> I'd hazzard a guess that anyone clever enough to know what the
> FreeBSD probe messages mean is probably clever enough to figure
> out "Escape" within about 4 keystrokes.  :)

Yes, but as has already been mentioned, the device probes are run with 
interrupts off, which means the keyboard press can't be detected?  In which case 
I suggest we simply add a boot option to the kernel to disable the splash 
screen, or perhaps overload "-v".  Then you can simply put, in small print at 
the bottom of the splash screen, "To disable this startup screen, boot with 
'-v'."  Sounds good?

-- Jake