From owner-freebsd-commit  Mon Nov  6 21:35:42 1995
Return-Path: owner-commit
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id VAA04161
          for freebsd-commit-outgoing; Mon, 6 Nov 1995 21:35:42 -0800
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id VAA04147
          for cvs-all-outgoing; Mon, 6 Nov 1995 21:35:36 -0800
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id VAA04133
          for cvs-sys-outgoing; Mon, 6 Nov 1995 21:35:31 -0800
Received: from jhome.DIALix.COM (root@jhome.DIALix.COM [192.203.228.69])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA04096
          ; Mon, 6 Nov 1995 21:34:55 -0800
Received: (from peter@localhost) by jhome.DIALix.COM (8.6.12/8.6.9) id AAA07161; Tue, 7 Nov 1995 00:47:18 +0800
Date: Tue, 7 Nov 1995 00:47:18 +0800 (WST)
From: Peter Wemm <peter@jhome.DIALix.COM>
To: Poul-Henning Kamp <phk@freefall.freebsd.org>
cc: CVS-commiters@freefall.freebsd.org, cvs-sys@freefall.freebsd.org
Subject: Re: cvs commit: src/sys/kern kern_sysctl.c
In-Reply-To: <199511061618.IAA00513@freefall.freebsd.org>
Message-ID: <Pine.BSF.3.91.951107003843.4726D-100000@jhome.DIALix.COM>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-commit@FreeBSD.org
Precedence: bulk

On Mon, 6 Nov 1995, Poul-Henning Kamp wrote:
> phk         95/11/06 08:18:54
> 
>   Modified:    sys/sys   sysctl.h
>                sys/kern  kern_sysctl.c
>   Log:
>   On working the new sysctl vars a bit I realized that I needed more generality.
>   This is here now.  We can now access (the new) sysctl variables from the
>   kernel too and using functions to handle access is more sane now.
>   I will now attack sysctl variables in the rest of the kernel and get them
>   all converted to newspeak.

Umm, I've not been following your sysctl() work closely, and indeed I'm 
not too fresh on sysctl in general these days, but does sysctl(8) 
automatically adapt to new entries being added into the kernel?

It's all done with linker_sets, right?  Is there any chance of getting 
the system to automatically catalog all the sysctl's?  for example, 
'sysctl vm' only returns one entry now; vm.loadavg.  Would it make sense 
for there to be a sysctl entry point per level that gave a catalog of all 
the other sysctl names at that level?  Then sysctl(8) could ask for all 
the names at the "vm" level, and print "unknown structure returned" if 
appropriate, or integers/etc when it gets them.

Of course, I dont really know what I'm talking about.. :-) If I'm 
speaking shit, please inform me politely.. :-)   If this is what you're 
working towards, I'll apologise and shut up.. :-)

Cheers,
-Peter