From owner-freebsd-hackers Sat Jul 25 15:50:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10911 for freebsd-hackers-outgoing; Sat, 25 Jul 1998 15:50:25 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles156.castles.com [208.214.165.156]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10904 for ; Sat, 25 Jul 1998 15:50:22 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA05792; Sat, 25 Jul 1998 11:43:15 -0700 (PDT) Message-Id: <199807251843.LAA05792@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Robert Withrow cc: wjw@IAEhv.nl, hackers@FreeBSD.ORG Subject: Re: SYSCTL ....... In-reply-to: Your message of "Sat, 25 Jul 1998 08:29:08 EDT." <199807251229.IAA06297@spooky.rwwa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 25 Jul 1998 11:43:14 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Another question (to the community): > > Have the FreeBSD *architects* weigh in on the value of the sytsctl approach > as opposed to, say, something like a "sysctl" filesystem (like the proc > filesystem)? Yes, there was a discussion on it a while back; you should be able to locate the thread(s) by searching the archives (hackers IIRC) for 'sysctlfs'. Opinions were divided, but I think that the 'against's were sufficiently convincing at the time. > Also, is this interface expected to be exposed via SNMP? Only indirectly, via an agent that has the opportunity to hold a set of OID:name mappings without forcing the mappings into the kernel. -- \\ 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