From owner-freebsd-hackers  Sun Nov  3 02:01:25 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id CAA11900
          for hackers-outgoing; Sun, 3 Nov 1996 02:01:25 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA11892
          for <freebsd-hackers@freebsd.org>; Sun, 3 Nov 1996 02:01:20 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id UAA29293; Sun, 3 Nov 1996 20:59:16 +1100
Date: Sun, 3 Nov 1996 20:59:16 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199611030959.UAA29293@godzilla.zeta.org.au>
To: bde@zeta.org.au, phk@critter.tfs.com
Subject: Re: Verbose babble in if_fddisubr.c
Cc: freebsd-hackers@freebsd.org, j@ida.interface-business.de
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>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.

The slice code already has a variable to tweak (dsi_debug), but I think
there shouldn't be many such variables.  The ones that exist should
be grouped together and initially set to the value of bootverbose.
bootverbose should be a sysctl variable and tweaking it should tweak
all the related variables.

Bruce