From owner-freebsd-current Sat Jan 9 18:49:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17651 for freebsd-current-outgoing; Sat, 9 Jan 1999 18:49:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles156.castles.com [208.214.165.156]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17645; Sat, 9 Jan 1999 18:49:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA02550; Sat, 9 Jan 1999 18:45:27 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901100245.SAA02550@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrzej Bialecki cc: freebsd-current@FreeBSD.ORG, Mike Smith Subject: Re: sysctl's as an FS In-reply-to: Your message of "Sun, 10 Jan 1999 00:35:42 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 09 Jan 1999 18:45:27 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello, > > I'm not sure if this idea has been already discussed... It occured to me > that since we need some dynamic approach to the sysctl mechanism (which > presently is static, constructed at compile time), especially when KLDs > should be able to insert/delete whole subtrees in it, why not reimplement > it in similar way to procfs? Because procfs' design is not adequately dynamic, unfortunately. I looked at this back when the syctlfs discussion came up. I also started on a generic meta-filesystem framework as a learning exercise, but I doubt I will finish it anytime soon. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message