From owner-freebsd-arch Fri Jul 14 2:14:20 2000 Delivered-To: freebsd-arch@freebsd.org Received: from ywing.creative.net.au (ywing.creative.net.au [203.56.168.34]) by hub.freebsd.org (Postfix) with ESMTP id 8F7B737BD15; Fri, 14 Jul 2000 02:14:13 -0700 (PDT) (envelope-from adrian@ywing.creative.net.au) Received: (from adrian@localhost) by ywing.creative.net.au (8.9.3/8.9.3) id LAA20845; Fri, 14 Jul 2000 11:21:18 +0200 (CEST) (envelope-from adrian) Date: Fri, 14 Jul 2000 11:21:17 +0200 From: Adrian Chadd To: Matthew Dillon Cc: Adrian Chadd , Andrzej Bialecki , freebsd-arch@FreeBSD.ORG Subject: Re: SysctlFS Message-ID: <20000714112117.D17372@ywing.creative.net.au> References: <20000712144510.A11316@ywing.creative.net.au> <200007130537.WAA29614@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007130537.WAA29614@apollo.backplane.com>; from dillon@apollo.backplane.com on Wed, Jul 12, 2000 at 10:37:50PM -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 12, 2000, Matthew Dillon wrote: > > :... > :> to the names should still be retrieved in binary form, as they are > :> exported via SYSCTL_* macros. But filesystem paradigm would allow us to > :> reuse all the concepts for hierarchical name handling, traversal, > :> permissions etc... The sysctlFS nodes would be probably read-only from > :> userland, as I don't see much sense in userland programs renaming or > :> removing them - they would be created, named and removed from > :> kernel-land. But things like traversal and access would be simplified > :> greatly. > :> > :> Any thoughts? > : > :I'm probably going to poke at it in a few weeks as an "example filesystem" > :for some documentation I'm writing up. There are issues in having it as > :a filesystem - see how /proc needs to be handled for jails right now. > :I'm sure other people on the list can fill you in .. :) > : > : > :Adrian > : > :-- > :Adrian Chadd Build a man a fire, and he's warm for the > : rest of the evening. Set a man on fire and > > I will point out that Linux puts system config variables in /proc and > it has been an unmitigated disaster. Well, maybe not *that bad*, but > it's fairly obvious to me that putting the config variables in a > filesystem yields absolutely *NO* advantage over having a system call > (and /sbin util) to do it. > > The current sysctl methodology works just dandy, we should not mess with > it. Oh, I agree. Hence why I said I'd write it up as an "example filesystem" .. I'm tossing up a few candidates at the moment. -- Adrian Chadd Build a man a fire, and he's warm for the rest of the evening. Set a man on fire and he's warm for the rest of his life. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message