Date: Mon, 17 Feb 1997 11:33:17 +1100 (EST) From: "Daniel O'Callaghan" <danny@panda.hilink.com.au> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: Eivind Eklund <eivind@dimaga.com>, giles@nemeton.com.au, avalon@coombs.anu.edu.au, jehamby@lightside.com, hackers@freebsd.org Subject: Re: boot messages (Was: Sun Workshop compiler vs. GCC?) Message-ID: <Pine.BSF.3.91.970217112912.8268F-100000@panda.hilink.com.au> In-Reply-To: <199702162320.JAA05708@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 17 Feb 1997, Michael Smith wrote: > Eivind Eklund stands accused of saying: > > > > How difficult early is it possible to switch to another vty? If this is > > possible to do real early, we can have a splash screen on the second vty, > > and "knowledgable people" will know they can switch back with ALT-F1. > > All screens should be cleared on finished boot, of course, unless the > > system is set up to boot directly to xdm. > > The splash-screen is actually implemented as an alternate display mode for > a single VT. But you're not paying attention : it is NOT POSSIBLE to > detect keystrokes on the console while the device probes are running, > because interrupts are Turned Off. > > Once interrupts are enabled, the hotkey toggles the screen. Seems to me that the most logical and expedient thing to so is to put a little more text into the "boot: " message. Something like "boot -t for text-mode boot". The other idea which was tossed about some months ago was to skip the splash screen if the image file (/splash.tiff) is not located in /, which makes it very easy to turn splash on/off for the next boot. Danny
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.970217112912.8268F-100000>