From owner-freebsd-hackers  Tue Jun  2 16:08:48 1998
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA00185
          for freebsd-hackers-outgoing; Tue, 2 Jun 1998 16:08:48 -0700 (PDT)
          (envelope-from owner-freebsd-hackers@FreeBSD.ORG)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA00172;
          Tue, 2 Jun 1998 16:08:37 -0700 (PDT)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id QAA18235;
	Tue, 2 Jun 1998 16:07:56 -0700 (PDT)
Message-Id: <199806022307.QAA18235@implode.root.com>
To: dyson@FreeBSD.ORG
cc: mike@dingo.cdrom.com (Mike Smith), mike@smith.net.au, hackers@FreeBSD.ORG
Subject: Re: kernfs/procfs questions... 
In-reply-to: Your message of "Tue, 02 Jun 1998 11:50:32 CDT."
             <199806021650.LAA02867@dyson.iquest.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 02 Jun 1998 16:07:56 -0700
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>Mike Smith said:
>> 
>> Sure; but can't these sort of improvements be made to the methods for 
>> manipulating procfs nodes?  What other drawbacks are there to the FS 
>> model?
>> 
>It is bogus that writing to a file "controls" something inside
>the system, that is kind-of what SNMP is for.  Now, if someone
>wants a kernfs that is compatible with our sysctl, they should
>be able to use the sysctl info to build the kernfs. 

   I can see it now: sysctlfs :-)

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message