From owner-cvs-sys  Sat Sep 28 10:04:36 1996
Return-Path: owner-cvs-sys
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA21230
          for cvs-sys-outgoing; Sat, 28 Sep 1996 10:04:36 -0700 (PDT)
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 KAA21152;
          Sat, 28 Sep 1996 10:04:27 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id DAA00970; Sun, 29 Sep 1996 03:03:31 +1000
Date: Sun, 29 Sep 1996 03:03:31 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199609281703.DAA00970@godzilla.zeta.org.au>
To: bde@FreeBSD.org, phk@critter.tfs.com
Subject: Re: cvs commit: src/sys/kern kern_mib.c
Cc: cvs-all@FreeBSD.org, CVS-committers@FreeBSD.org, cvs-sys@FreeBSD.org
Sender: owner-cvs-sys@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>>  - all the user sysctls were read-write (and thus it was possible for them
>>    to be inconsistent with the authoritative fixed values in the library).
>
>They would never be accessed in the kernel, they're only there as place-
>holders in the name-space.

Oops.  I see that the can't be accessed by sysctl(2).  Are there other
access functions that walk in the places they hold?

Bruce