From owner-freebsd-arch Wed Jul 26 18:47:41 2000 Delivered-To: freebsd-arch@freebsd.org Received: from beastie.mckusick.com (beastie.mckusick.com [209.31.233.184]) by hub.freebsd.org (Postfix) with ESMTP id 6C6AC37BF39 for ; Wed, 26 Jul 2000 18:47:35 -0700 (PDT) (envelope-from mckusick@mckusick.com) Received: from beastie.mckusick.com (localhost [127.0.0.1]) by beastie.mckusick.com (8.9.3/8.9.3) with ESMTP id SAA16199; Wed, 26 Jul 2000 18:47:34 -0700 (PDT) (envelope-from mckusick@beastie.mckusick.com) Message-Id: <200007270147.SAA16199@beastie.mckusick.com> To: Andrzej Bialecki Subject: Re: SysctlFS Cc: freebsd-arch@FreeBSD.ORG In-Reply-To: Your message of "Wed, 12 Jul 2000 14:45:10 +0200." <20000712144510.A11316@ywing.creative.net.au> Date: Wed, 26 Jul 2000 18:47:34 -0700 From: Kirk McKusick Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Date: Wed, 12 Jul 2000 14:45:10 +0200 From: Adrian Chadd To: Andrzej Bialecki Cc: freebsd-arch@FreeBSD.ORG Subject: Re: SysctlFS 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. > If you are still interested in doing this, see `man kernfs' which is a prototype of a filesystem designed to show (and in some cases modify) kernel information. Kirk McKusick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message