From owner-freebsd-chat  Sun Feb 16 17:35:51 1997
Return-Path: <owner-chat>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA12266
          for chat-outgoing; Sun, 16 Feb 1997 17:35:51 -0800 (PST)
Received: from darkstar (dialin1.anlw.anl.gov [141.221.252.101])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA12257
          for <freebsd-chat@freebsd.org>; Sun, 16 Feb 1997 17:35:45 -0800 (PST)
Received: (from cmott@localhost) by darkstar (8.6.12/8.6.12) id SAA01498; Sun, 16 Feb 1997 18:35:40 -0700
Date: Sun, 16 Feb 1997 18:35:39 -0700 (MST)
From: Charles Mott <cmott@srv.net>
X-Sender: cmott@darkstar
To: freebsd-chat@freebsd.org
Subject: Re: boot messages (Was: Sun Workshop compiler vs. GCC?)
In-Reply-To: <Pine.BSF.3.91.970217112912.8268F-100000@panda.hilink.com.au>
Message-ID: <Pine.BSF.3.91.970216182016.1345B-100000@darkstar>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-chat@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

moved to -chat

I concur with others that high quality graphics during boot up would help
build up the FreeBSD user base (should this be a goal?).  One thing that
distinguishes Walnut Creek is that they have a better sense of graphical
design and packaging than the other cdrom outfits.

If graphics and aesthetics weren't important, then we would mostly be
using monochrome monitors. 

As long as the splash screen can be disabled with and escape, I think it 
should be fine.  The device probes are useful when bringing up a news 
system (mainly to see where things hang up), but after that, the dmesg 
command is how I look at that information.

Charles Mott