From owner-freebsd-hackers Tue May 8 4:41:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 977A337B422 for ; Tue, 8 May 2001 04:41:06 -0700 (PDT) (envelope-from des@ofug.org) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id NAA56280; Tue, 8 May 2001 13:40:41 +0200 (CEST) (envelope-from des@ofug.org) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: Sheldon Hearn Cc: hackers@freebsd.org Subject: Re: sysctl(8) and opaque MIB entries References: <5954.989307088@axl.fw.uunet.co.za> From: Dag-Erling Smorgrav Date: 08 May 2001 13:40:40 +0200 In-Reply-To: <5954.989307088@axl.fw.uunet.co.za> Message-ID: Lines: 15 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn writes: > That would meet my needs. Are you sure this is a better route than > allowing a "limiting parent node" to be specified along with -A and -a? > Seems to me that the latter would avoid introducing yet more options and > the functionality I'm proposing seems intuitive to me and Peter at > least. :-) Maybe so, but I've always thought -A and -X were *counter*intuitive, and the current behaviour of 'sysctl foo' where foo is the name of an opaque variable is, to say the least, surprising. Adding the -x option makes it slightly less so. DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message