From owner-cvs-all Thu May 21 09:54:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09710 for cvs-all-outgoing; Thu, 21 May 1998 09:54:17 -0700 (PDT) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles216.castles.com [208.214.165.216]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA09647; Thu, 21 May 1998 09:54:05 -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 IAA03281; Thu, 21 May 1998 08:00:30 -0700 (PDT) Message-Id: <199805211500.IAA03281@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Joao Carlos Mendes Luis cc: hasty@rah.star-gate.com (Amancio Hasty), bde@zeta.org.au, jkh@time.cdrom.com, ahasty@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG, cvs-sys@FreeBSD.ORG, luigi@labinfo.iet.unipi.it, roger@cs.strath.ac.uk Subject: Re: cvs commit: src/sys/pci brooktree848.c In-reply-to: Your message of "Thu, 21 May 1998 11:24:52 -0300." <199805211424.LAA15001@roma.coe.ufrj.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 May 1998 08:00:30 -0700 From: Mike Smith Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk > #define quoting(Amancio Hasty) > // Actually, it is more natural to standardized around a unified interface > > Yes... Agreed. > // If I want to find out all the bt848 devices on the system: > // sysctl hw.bt848 > // which does a snmplike walk on the node hw.bt848 > > This is not the SNMP way. Mentioning SNMP was a Bad Idea. > // Incidentely, you can still maintain the device control programs as shell > // wrappers which just use sysctl commands;however, the converse is not true. > > I have one doubt on the subject. Device control can always have > permissions controlled on the file node. What about sysctls ? Good point, and one for Garrett's desire to see the parameter space take on filesystem semantics. The problem with using the filesystem itself for this is the same problem that /dev has - there is no direct association between the real parameter space and the access points. DEVFS begins the process of addressing this, and you could do the same with a SYSCTLFS, however neither of these address the persistence issue usefully. > sysctls are good for monitoring and/or settings defaults at rc.local, > but not for final user control. That's why I still have no position > on this discussion. My position is that sysctl is the choice, then > it must look like SNMP. Period. I am likewise a little indecisive, but quite certain that emulating SNMP slavishly (as opposed to learning from it) would be a mistake. -- \\ 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 cvs-all" in the body of the message