From owner-freebsd-arch Wed Jul 12 5:38:16 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 C548E37BB71 for ; Wed, 12 Jul 2000 05:38:09 -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 OAA11336; Wed, 12 Jul 2000 14:45:10 +0200 (CEST) (envelope-from adrian) Date: Wed, 12 Jul 2000 14:45:10 +0200 From: Adrian Chadd To: Andrzej Bialecki Cc: freebsd-arch@FreeBSD.ORG Subject: Re: SysctlFS Message-ID: <20000712144510.A11316@ywing.creative.net.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from abial@webgiro.com on Wed, Jul 12, 2000 at 01:35:47PM +0200 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 12, 2000, Andrzej Bialecki wrote: > Hi, > > I've been tweaking the sysctls here and there for some time now, and I'd > like to see what is the current opinion on implementing sysctl tree as a > filesystem. Most of the work I've done with dynamic sysctls is very > similar to what happens with filesystem. Also, filesystem model allows for > much more fine-grained access control. > > I'm opposed to the idea of having something similar like Linux /proc, > though, with nice formatting done in the kernel... The objects hooked up > 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 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