From owner-freebsd-hackers Mon May 7 10:44: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 0664737B423 for ; Mon, 7 May 2001 10:44:00 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.3/8.11.3) with ESMTP id f47Hhd849826; Mon, 7 May 2001 19:43:39 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Sheldon Hearn Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG Subject: Re: sysctl(8) and opaque MIB entries In-Reply-To: Your message of "Mon, 07 May 2001 19:20:23 +0200." <99353.989256023@axl.fw.uunet.co.za> Date: Mon, 07 May 2001 19:43:39 +0200 Message-ID: <49824.989257419@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <99353.989256023@axl.fw.uunet.co.za>, Sheldon Hearn writes: > > >On 07 May 2001 18:51:22 +0200, Dag-Erling Smorgrav wrote: > >> Yes it will, with -X. The interesting question is why there isn't an >> option to make it display just one variable in hex, and why it doesn't >> print a message when it omits printing an opaque variable. > >Do you think it'd be okay to allow an argument to -a and -A that >specifies the sysctl node from which to descend? You mean like # sysctl vfs.devfs vfs.devfs.noverflow: 32768 vfs.devfs.generation: 116 vfs.devfs.inodes: 116 vfs.devfs.topinode: 118 :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message