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 Message-ID: <Pine.BSF.3.91.951107003843.4726D-100000@jhome.DIALix.COM> In-Reply-To: <199511061618.IAA00513@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.951107003843.4726D-100000>