From owner-freebsd-hackers Mon Jun 28 3: 1:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 9142C14CD1 for ; Mon, 28 Jun 1999 03:01:29 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA87884; Mon, 28 Jun 1999 11:00:29 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 28 Jun 1999 11:00:29 +0100 (BST) From: Doug Rabson To: Alan Cox Cc: viro@math.psu.edu, sommerfeld@orchard.arlington.ma.us, fare@tunes.org, linux-kernel@vger.rutgers.edu, freebsd-hackers@freebsd.org, tech-kern@netbsd.org Subject: Re: Improving the Unix API In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Jun 1999, Alan Cox wrote: > > As far as sysctl goes, FreeBSD deprecates the use of numbers for OIDs and > > has a string-based mechanism for exploring the sysctl tree. > > So we are actually both going the same way. Linus with /proc/sys and his > official dislike of sysctl (Oh well I think sysctl using number spaces is the > right idea - like snmp is), and BSD going to names As far as I know, only FreeBSD has a string-based sysctl implementation. Something which always confused me about Linux' procfs - what have all these kernel variables got to do with process state? We used to have a kernfs which was intended for this kind of thing but it rotted after people started extending sysctl for the purpose. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message