From owner-freebsd-hackers Tue Jun 2 14:11:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10025 for freebsd-hackers-outgoing; Tue, 2 Jun 1998 14:11:49 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10013; Tue, 2 Jun 1998 14:11:37 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA00370; Tue, 2 Jun 1998 13:06:58 -0700 (PDT) Message-Id: <199806022006.NAA00370@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: dyson@FreeBSD.ORG cc: 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 02 Jun 1998 13:06:58 -0700 From: Mike Smith 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. So you don't believe in device files? Or the "everything is a file" model cf. Plan 9? Hmm. -- \\ 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-hackers" in the body of the message