From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 19 19:52:23 2006 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 4F26F16A40F for ; Tue, 19 Dec 2006 19:52:23 +0000 (UTC) (envelope-from soralx@cydem.org) Received: from cydem.org (S0106000103ce4c9c.vc.shawcable.net [24.87.27.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25CAF43CB8 for ; Tue, 19 Dec 2006 19:52:18 +0000 (GMT) (envelope-from soralx@cydem.org) Received: from freen0de (unknown [192.168.0.251]) by cydem.org (Postfix/FreeBSD) with ESMTP id 267D491EDC; Tue, 19 Dec 2006 11:23:15 -0800 (PST) Date: Tue, 19 Dec 2006 11:23:10 -0800 From: To: Message-ID: <20061219112310.69a8ba47@freen0de> In-Reply-To: <4587F6F1.1050000@metro.cx> References: <4587F6F1.1050000@metro.cx> X-Mailer: Sylpheed-Claws 2.5.2 (GTK+ 2.10.6; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: unique hardware identification X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Dec 2006 19:52:23 -0000 > I'm thinking of something like combining serial numbers from > CPU/disks for example, but there does not seem to be a clear way to > obtain these (not all cpu's even have a serial number in there). the simplest thing that comes to my mind is parsing `dmidump` for serial numbers, hoping there are some... (there are a few in the dump I obtained, but it's a laptop) [SorAlx] ridin' VN1500-B2