From owner-freebsd-hackers Sat Nov 25 21:24:57 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA13668 for hackers-outgoing; Sat, 25 Nov 1995 21:24:57 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA13651 for ; Sat, 25 Nov 1995 21:24:39 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA16597; Sun, 26 Nov 1995 16:23:21 +1100 Date: Sun, 26 Nov 1995 16:23:21 +1100 From: Bruce Evans Message-Id: <199511260523.QAA16597@godzilla.zeta.org.au> To: hackers@freebsd.org, peter@taronga.com Subject: Re: machine reboot & kernel maxusers option Sender: owner-hackers@freebsd.org Precedence: bulk >>I really don't like the two dozen ``foo: not found at address ...'' >>messages for the installation kernel. >I like it. A lot. I hate systems that don't tell me what the hell they're >doing on boot-up (see also, Windows NT, SCO, Unixware). I like them too, but the message buffer isn't large enough for many more. Yesterday I tested 23 extended DOS partitions D: to Z: and the message buffer filled up with messages about strange partition data, overwriting more important messages. A message buffer in libdisk filled up and overwrote the stack. The kernel message buffer should be much larger until syslogd can be run. >How about at least an "options BOOTVERBOSE" for us belt-and-suspenders types? Note that the `bootverbose' flag is not a verbose booting flag; it is a verbose flag that is set at boot time and happens to be used more while booting. There should be a sysctl to control it after booting and some way to set the defaults for all boot-control values Bruce