From owner-freebsd-hackers Sun Sep 22 15:32:46 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA21441 for hackers-outgoing; Sun, 22 Sep 1996 15:32:46 -0700 (PDT) Received: from alpo.whistle.com (s205m1.whistle.com [207.76.205.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA21368 for ; Sun, 22 Sep 1996 15:32:33 -0700 (PDT) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.7.5/8.7.3) with SMTP id PAA17646; Sun, 22 Sep 1996 15:24:56 -0700 (PDT) Message-ID: <3245BC3E.237C228A@whistle.com> Date: Sun, 22 Sep 1996 15:22:54 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0b6 (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Jake Hamby CC: Warner Losh , Joe Greco , Terry Lambert , brandon@glacier.cold.org, freebsd-hackers@FreeBSD.org Subject: Re: splash-page on bootup.. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jake Hamby wrote: > > > > Maybe the best idea would be to have a -q mode that boots quietly so > > that you can do the blue screen trick, and then a little later start > > up X windows and see very little in the way of booting junk. After > > all, what NT does it turn the screen blue, print a terse message that > > says it is coming up, then starts Windows as soon as it is able, and > > then continues bringing up the rest of the system. I seem to recall > > that one of its loader stages does this. > > I think this is the best idea yet! Turn the background blue, the > foreground white, and draw a few cheezy curses-looking boxes and a status > bar. If you notice, both FreeBSD and Slackware Linux's SETUP programs > have this look, as does the MS-DOS SETUP program. :-) > > Then recode the probe messages to print in the appropriate part of the > screen, bump the status bar up at various stages of the boot process, and > voila! A "professional" boot sequence. Especially if OEM's can customize > the various messages and colors to give their version a unique look. > > -- Jake We can simply have the syscons switch to vt1 and if you want the real stuff you can make it NOT do that, or even switch back to vt0 yourself