From owner-freebsd-hackers Sat Feb 15 16:06:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA26660 for hackers-outgoing; Sat, 15 Feb 1997 16:06:23 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA26620 for ; Sat, 15 Feb 1997 16:06:15 -0800 (PST) Message-Id: <199702160006.QAA26620@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA076481531; Sun, 16 Feb 1997 11:05:31 +1100 From: Darren Reed Subject: Re: Sun Workshop compiler vs. GCC? To: jehamby@lightside.com (Jake Hamby) Date: Sun, 16 Feb 1997 11:05:30 +1100 (EDT) Cc: hackers@freebsd.org In-Reply-To: <199702152232.OAA05103@lightside.com> from "Jake Hamby" at Feb 15, 97 02:32:00 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In some mail from Jake Hamby, sie said: [...] > See my previous post (which I cc:ed to config, not hackers, as per Jordan's > suggestion), in which I discuss what Solaris does when it boots (logs > hardware probes to syslog by default, not the console), and why we should > keep FreeBSD the way it is (because x86 hardware is difficult to configure > and people WANT the hardware probe messages). IMHO, that is a reflection of the diference in the knowledege of the average user of FreeBSD compared with Solaris. To those of us here, and probably 99% of those running FreeBSD, those probe messages mean something. Are they likely to mean anything to a secretary ? Another take on starting up is HP-UX 10. Being SVR4, it has run levels and start/stop scripts. HP have added "startmsg" and "stopmsg" to all their scripts, so that when you boot, it prints a menu type listing and displays "OK", "BUSY", "N/A", "FAIL" in the little check box for each rc script. With about 16 per screen, it clears the screen when it gets to the bottom and presents a new menu. It _looks_ very professional and is very informative (stderr/stdout for all rc scripts goes to a file). Darren