From owner-cvs-sys  Sat Sep 28 10:10:05 1996
Return-Path: owner-cvs-sys
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA23993
          for cvs-sys-outgoing; Sat, 28 Sep 1996 10:10:05 -0700 (PDT)
Received: from critter.tfs.com ([140.145.230.177])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA23896;
          Sat, 28 Sep 1996 10:09:54 -0700 (PDT)
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 TAA00674; Sat, 28 Sep 1996 19:09:27 +0200 (MET DST)
To: Bruce Evans <bde@zeta.org.au>
cc: bde@FreeBSD.org, cvs-all@FreeBSD.org, CVS-committers@FreeBSD.org,
        cvs-sys@FreeBSD.org
Subject: Re: cvs commit: src/sys/kern kern_mib.c 
In-reply-to: Your message of "Sun, 29 Sep 1996 03:03:31 +1000."
             <199609281703.DAA00970@godzilla.zeta.org.au> 
Date: Sat, 28 Sep 1996 19:09:27 +0200
Message-ID: <672.843930567@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-cvs-sys@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199609281703.DAA00970@godzilla.zeta.org.au>, Bruce Evans writes:
>>>  - 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?

No, only the sneaky "get-next" pseudo variable under the "sysctl" part
of the tree.

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