From owner-freebsd-hackers Thu Oct 31 10:44:34 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA27165 for hackers-outgoing; Thu, 31 Oct 1996 10:44:34 -0800 (PST) Received: from mailer.syr.edu (mailer.syr.edu [128.230.20.20]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA27155 for ; Thu, 31 Oct 1996 10:44:24 -0800 (PST) Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.0a) with SMTP id 6DD9DD20 ; Thu, 31 Oct 1996 13:42:59 -0500 Received: from localhost (cmsedore@localhost) by rodan.syr.edu (8.7.6/8.7.3) with SMTP id NAA00639 for ; Thu, 31 Oct 1996 13:44:13 -0500 (EST) X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs Date: Thu, 31 Oct 1996 13:44:12 -0500 (EST) From: Christopher Sedore X-Sender: cmsedore@rodan.syr.edu Reply-To: Christopher Sedore To: freebsd-hackers@FreeBSD.org Subject: Re: Verbose babble in if_fddisubr.c In-Reply-To: <6078.846772188@critter.tfs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 31 Oct 1996, Poul-Henning Kamp wrote: > >The author of `bootverbose' told me that it was a general flag when I > >objected to using it for controlling the slice messages. > > Is that's me you're referring to ? :-) > > The idea was for it to be a flag that you could set so early that you > could catch boot-related stuff (to which I consider the slice but > not the FDDI messages). As soon as you have single user running > you can tweak a sysctl variable, and things that can use that, > should use that instead. > > So: FDDI should have a sysctl: > > net.fddi.verbose > > or similar, possibly two different ones... I'd argue against this approach. The printf()s in the FDDI code print out one message per packet of an unknown protocol (IPX, Appletalk, etc). On my console, this is an average of something like 1-3 lines per second. I can't imagine an actual use for this other than debugging. This would be like printing out a line for every non-IP ethernet packet received: this isn't a "verbose" mode, this is a debug mode, much like SCSI_DEBUG or whatever the define is that prints out all the SCSI commands/transfers. Unless I'm missing the point of verbose, it seems that this would limit the utility of verbose by producing enough output to drown out everything else printed. -Chris