From owner-freebsd-hackers Thu Oct 31 06:30:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id GAA09623 for hackers-outgoing; Thu, 31 Oct 1996 06:30:11 -0800 (PST) Received: from critter.tfs.com (disn4.cybercity.dk [194.16.57.4]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA09560; Thu, 31 Oct 1996 06:29:56 -0800 (PST) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id PAA06080; Thu, 31 Oct 1996 15:29:48 +0100 (MET) To: Bruce Evans cc: freebsd-hackers@freebsd.org, j@ida.interface-business.de Subject: Re: Verbose babble in if_fddisubr.c In-reply-to: Your message of "Fri, 01 Nov 1996 01:02:49 +1100." <199610311402.BAA00660@godzilla.zeta.org.au> Date: Thu, 31 Oct 1996 15:29:48 +0100 Message-ID: <6078.846772188@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >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... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so.