From owner-freebsd-arch@FreeBSD.ORG Fri Nov 9 17:20:23 2007 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5C2116A468 for ; Fri, 9 Nov 2007 17:20:23 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.185]) by mx1.freebsd.org (Postfix) with ESMTP id 4260C13C4B7 for ; Fri, 9 Nov 2007 17:20:23 +0000 (UTC) (envelope-from qpadla@gmail.com) Received: by fk-out-0910.google.com with SMTP id b27so650424fka for ; Fri, 09 Nov 2007 09:20:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; bh=iCYW/Jl3ohZT/V6rVfEs6ZsrHVY2A+ZKgntW9MkS44k=; b=lNexS+vkrDwGV9r0+MUTd5v657ioVaYhxbdbcIeJWxyb5Qp38Dcg3ZzqjwQ9vlKeUZRTsLzoiOpHC42nM8cJIdgathuS+jvkQtOxaxTMhUy6ssC+TSCqkA7Qch5R1Z3FV70lsUgKtLf5beiKFLmAJmaf/ifEwrPMuMgxMV0Ljq0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:reply-to:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id; b=oxb2NhL5EDCZav+pLb6ImDXRobXFcv71b1JZTvE23dELo+i1TKAVZBAgVKAkEyiOiftlHDgB4xrHmaEGHbHfruYNzlBZ4LD9V5LBSAHv92JRYSNoyJ6LbZEHfZFWfjthMkO6LMsqF2ADzLN8RHhMzbEbOUgPLSbmrVai4Ygfdyw= Received: by 10.82.175.17 with SMTP id x17mr4294843bue.1194627215868; Fri, 09 Nov 2007 08:53:35 -0800 (PST) Received: from orion ( [89.162.141.1]) by mx.google.com with ESMTPS id y2sm4711816mug.2007.11.09.08.53.32 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 09 Nov 2007 08:53:34 -0800 (PST) From: Nikolay Pavlov To: freebsd-arch@freebsd.org Date: Fri, 9 Nov 2007 18:51:10 +0200 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) References: <20071109124421.3c1901b1@deskjail> In-Reply-To: <20071109124421.3c1901b1@deskjail> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3093353.TiXXcl7AEI"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200711091851.19445.qpadla@gmail.com> Cc: cnst@freebsd.org, arch@freebsd.org, rwatson@freebsd.org, Alexander Leidinger , imp@freebsd.org Subject: Re: sensors framework continued (architecture) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: qpadla@gmail.com List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Nov 2007 17:20:24 -0000 --nextPart3093353.TiXXcl7AEI Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 09 November 2007 13:44:21 Alexander Leidinger wrote: > Robert thinks that sysctl MIBs offer "a more semantically rich and, to > be honest, better defined way of interacting with live subsystems than > device files do in a generic sense". Nobody objected to this opinion or > provided reasons why a fd based approach is better than a sysctl MIB > based approach. Ricardo Nabinger Sanchez points out > http://www.ietf.org/rfc/rfc3433.txt (RFC for sensor MIBs). I think a MIB approach is much more usefull between "Single-system sensors= =20 framework" and "Group-level sensors framework" and a good example here is=20 a SNMP(the general usage example of the MIB defined in rfc3433). I am not=20 a kernel developer and don't know whether it's a good for pass the data or= =20 not, but as experienced administrator should mansion that sysctl mib's is=20 expected (IMHO) to be used as a configuration interface to define a kernel= =20 and system behavior. It's much more easy to use userland utilities such as= =20 vmstat, systat, netstat, sockstat than listing some stats and data via=20 sysctl. Also i suspect that such complex and rich thing as sensors=20 framework often would be a subject to various changes and extensions, so i= =20 vote to hide kernel part as much as possible.=20 =2D-=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 =2D Best regards, Nikolay Pavlov. <<<----------------------------------- = =20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 --nextPart3093353.TiXXcl7AEI Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBHNJAH/2R6KvEYGaIRAgkhAJ44iVEo9wz2IpZiZ3wlacG/iqifBwCfaEkn /6NDikrU+K+mbEd7WeAwVX8= =vPmq -----END PGP SIGNATURE----- --nextPart3093353.TiXXcl7AEI--