Date: Wed, 30 Oct 1996 17:48:08 +0100 From: se@zpr.uni-koeln.de (Stefan Esser) To: joerg_wunsch@interface-business.de (Joerg Wunsch) Cc: freebsd-hackers@FreeBSD.org (FreeBSD hackers) Subject: Re: Verbose babble in if_fddisubr.c Message-ID: <199610301649.RAA06483@x14.mi.uni-koeln.de> In-Reply-To: <199610301638.RAA06231@ida.interface-business.de>; from J Wunsch on Oct 30, 1996 17:38:32 %2B0100 References: <199610301638.RAA06231@ida.interface-business.de>
next in thread | previous in thread | raw e-mail | index | archive | help
J Wunsch writes: > Hi all, > > i've just got a call by a customer who's using a DEC DEFPA FDDI card > now. She told me that everything works fine (once i've pointed her to > the `pseudo-device fddi') but has been a little scared by some verbose > babble caused by the driver. ... > I think both printf's are merely nice debugging aids to see all the > garbage that flies along your wire :), but nothing to be dropped onto > a regular user. I therefore suggest hiding them inside either some > #ifdef, or at least behind `bootverbose'. How about adding a "sysctl" variable for that purpose ? I'd be opposed to make "bootverbose" take over the meaning "produce more run-time debug messages", since this might affect its current use. But it might be a good idea to make bootverbose set the default for the "verbose run-time msgs" sysctl variable (and it can be forced to on or off from some rc script, if preferred) ... Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610301649.RAA06483>