From owner-freebsd-hackers@FreeBSD.ORG Fri Feb 2 17:00:34 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 127EE16A407 for ; Fri, 2 Feb 2007 17:00:34 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 90D4813C461 for ; Fri, 2 Feb 2007 17:00:33 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (wvmzsx@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l12H0KuY096687; Fri, 2 Feb 2007 18:00:26 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l12H0KIv096686; Fri, 2 Feb 2007 18:00:20 +0100 (CET) (envelope-from olli) Date: Fri, 2 Feb 2007 18:00:20 +0100 (CET) Message-Id: <200702021700.l12H0KIv096686@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG, dr2867@pacbell.net, peterjeremy@optushome.com.au In-Reply-To: <20070202070654.GD909@turion.vk2pj.dyndns.org> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Fri, 02 Feb 2007 18:00:30 +0100 (CET) Cc: Subject: Re: unique hardware identification X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG, dr2867@pacbell.net, peterjeremy@optushome.com.au List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2007 17:00:34 -0000 Peter Jeremy wrote: > Daniel Rudy wrote: > > None of this stuff appears on my system and I'm running 6.1. I can't > > even find dmidump anywhere on the system or in ports either. > > Please elaborate. kenv(8) states that it first appeared in 4.1.1 and > I don't recall seeing any reference to 'dmidump' in this thread. For retrieving DMI information, please see sysutils/dmidecode in the ports collection. It works fine on the HP Proliant machines here, it even reports the exact population of the RAM slots and other things, which makes remote administration easier. Of course, it only works on machines with DMI-compliant BIOS interface. If you don't get SMBIOS information, I very much doubt that it'll provide DMI information either. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "I have stopped reading Stephen King novels. Now I just read C code instead." -- Richard A. O'Keefe