From owner-freebsd-hardware@FreeBSD.ORG Mon Dec 6 23:03:06 2010 Return-Path: Delivered-To: hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE67F106564A for ; Mon, 6 Dec 2010 23:03:06 +0000 (UTC) (envelope-from avg@freebsd.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id F305A8FC18 for ; Mon, 6 Dec 2010 23:03:05 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id BAA16935; Tue, 07 Dec 2010 01:03:00 +0200 (EET) (envelope-from avg@freebsd.org) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1PPk5E-000DcF-9L; Tue, 07 Dec 2010 01:03:00 +0200 Message-ID: <4CFD6BA3.7070505@freebsd.org> Date: Tue, 07 Dec 2010 01:02:59 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.12) Gecko/20101029 Lightning/1.0b2 Thunderbird/3.1.6 MIME-Version: 1.0 To: "Mikhail T." References: <4CFC910A.5090806@aldan.algebra.com> <4CFD3EC0.1060600@fuckner.net> <4CFD5006.7010303@aldan.algebra.com> In-Reply-To: <4CFD5006.7010303@aldan.algebra.com> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: questions@freebsd.org, hardware@freebsd.org Subject: Re: monitoring hardware temperatures X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Dec 2010 23:03:06 -0000 on 06/12/2010 23:05 Mikhail T. said the following: > The sensors-patches did not add any new entries under hw.sensors hierarchy :( Oh good, one less potential source of "sensors framework" flames :-) Seriously, the version that was ported to FreeBSD was very desktop-ish, so no miracle was expected and none happened. BTW, you could probably write a simple script employing smbmsg(1) to query the DIMMs based on logic in the sdtemp driver. -- Andriy Gapon