From owner-freebsd-hackers  Sun Nov  5 02:33:14 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id CAA27676
          for hackers-outgoing; Sun, 5 Nov 1995 02:33:14 -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 CAA27670
          for <hackers@freebsd.org>; Sun, 5 Nov 1995 02:33:07 -0800
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id VAA32280; Sun, 5 Nov 1995 21:31:26 +1100
Date: Sun, 5 Nov 1995 21:31:26 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199511051031.VAA32280@godzilla.zeta.org.au>
To: graichen@sirius.physik.fu-berlin.de, grog@lemis.de
Subject: Re: machine reboot & kernel maxusers option
Cc: hackers@freebsd.org
Sender: owner-hackers@freebsd.org
Precedence: bulk

>> > I've been voting for hiding the ``not found'' messages behind the
>> > "bootverbose" (boot -v) case long ago, but nobody seems to agree. :)
>> >
>>  
>> i agree with you - i think this should be the sense of a "-v" flag - normally
>> you should'ne see what's missing (if it is something impotant you'll see it if
>> something is'nt working :-) - but you shoud have a chance to look more careful
>> at all the device probes (using boot -v)

>I'll go along with that.  "Not found" also scares off people who don't
>realize that it's a normal state of affairs.

It's only normal (and not good) for GENERIC and other bloated kernels.

Bruce