From owner-freebsd-arch Fri Jul 14 1:47:32 2000 Delivered-To: freebsd-arch@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 3213237BAD3; Fri, 14 Jul 2000 01:47:14 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA29614; Wed, 12 Jul 2000 22:37:50 -0700 (PDT) (envelope-from dillon) Date: Wed, 12 Jul 2000 22:37:50 -0700 (PDT) From: Matthew Dillon Message-Id: <200007130537.WAA29614@apollo.backplane.com> To: Adrian Chadd Cc: Andrzej Bialecki , freebsd-arch@FreeBSD.ORG Subject: Re: SysctlFS References: <20000712144510.A11316@ywing.creative.net.au> Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :... :> 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. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message