From owner-freebsd-arch@FreeBSD.ORG Sat Apr 7 20:54:13 2007 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F1BF616A401; Sat, 7 Apr 2007 20:54:13 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 9404013C4BC; Sat, 7 Apr 2007 20:54:13 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.8/8.13.4) with ESMTP id l37KqrbE021636; Sat, 7 Apr 2007 14:52:53 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 07 Apr 2007 14:53:01 -0600 (MDT) Message-Id: <20070407.145301.-345495730.imp@bsdimp.com> To: pjd@freebsd.org From: "M. Warner Losh" In-Reply-To: <20070407175439.GL63916@garage.freebsd.pl> References: <20070407120656.GD63916@garage.freebsd.pl> <4617CB2D.8000508@gmail.com> <20070407175439.GL63916@garage.freebsd.pl> X-Mailer: Mew version 4.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sat, 07 Apr 2007 14:52:53 -0600 (MDT) Cc: freebsd-arch@freebsd.org Subject: Re: Host ID. X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Apr 2007 20:54:14 -0000 In message: <20070407175439.GL63916@garage.freebsd.pl> Pawel Jakub Dawidek writes: : On Sat, Apr 07, 2007 at 06:47:41PM +0200, Pawel Worach wrote: : > Pawel Jakub Dawidek wrote: : > >Hi. : > >After initial discussion on IRC, I'd like to propose an addition... : > >I want to use it with ZFS, but I thought it may be useful in general, so : > >here it goes: : > >I'd like to assign a unique ID to the system on first boot. : > >When system starts, /etc/rc.d/hostid script checks if /hostid file : > >exists, if it doesn't, it creates it via 'uuidgen > /hostid'. : > >It will also set kern.hostuuid sysctl to this value and first four bytes : > >of MD5(kern.hostuuid) will be stored in kern.hostid. It will allow to : > >use gethostid(3). : > >If root file system is read-only, different uuid will be genrated on : > >each boot. Not sure if anything better can be done here. : > >As I said, I think it may be genrally useful. Imagine using it with : > >magic/variant symlinks, for example. : > >Comments? : > : > What about ... : > : > # kenv smbios.system.uuid : > 63F8BC81-475C-11CB-A074-CA3B9005F8F6 : > : > Not all systems have SMBIOSen but maybe it can be used instead of /{,etc}/hostid if available ? : : We thought about this, but as you noted it's not always available. I : want this to behave the same on each system. Windows almost requires this be present, so it is present in many systems. There are a number of things that we use the best source of information first, and only then do we fall back to something less suitable. I don't see why this would be any different, and it would give more systems a chance to work. Many systems that have other BIOS issues, such as: smbios.system.maker="To be Filled" smbios.system.product="To be Filled" smbios.system.serial="00000000" none-the-less have this filled in. A quick survey of all the machines I have shows that the following didn't have it: Sony VAIO 505-TS (Pentium 300MHz laptop) NEC PC9821Ra (pc98 with Pentium II 400MHz) Kwikbyte KB9202 (Atmel AT91RM9200 based eval board) AMI Mobo + dual core amd opeteron Some embedded SBCs which have smbios, but no uuid. and a bunch of 4.x and 5.x machines that pre-date the addition of the smbios code that I can't check. So it is a mixed bag. Warner