From owner-freebsd-arch@FreeBSD.ORG Sun Apr 8 13:15:09 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 E402716A404 for ; Sun, 8 Apr 2007 13:15:09 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout2-b.corp.dcn.yahoo.com (mrout2-b.corp.dcn.yahoo.com [216.109.112.28]) by mx1.freebsd.org (Postfix) with ESMTP id AE23313C458 for ; Sun, 8 Apr 2007 13:15:09 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy7.corp.yahoo.com [216.145.48.98]) by mrout2-b.corp.dcn.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id l38D4fs0023705; Sun, 8 Apr 2007 06:04:42 -0700 (PDT) Date: Sun, 08 Apr 2007 22:04:16 +0900 Message-ID: From: gnn@freebsd.org To: "M. Warner Losh" In-Reply-To: <20070407.145301.-345495730.imp@bsdimp.com> References: <20070407120656.GD63916@garage.freebsd.pl> <4617CB2D.8000508@gmail.com> <20070407175439.GL63916@garage.freebsd.pl> <20070407.145301.-345495730.imp@bsdimp.com> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.7 Emacs/22.0.95 (i386-apple-darwin8.8.2) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: pjd@freebsd.org, 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: Sun, 08 Apr 2007 13:15:10 -0000 I noted that someone mentioned using a network based ID. Since EUI-64 are unique I would suspect they would be the best source for this on systems that don't naturally have a hostid concept. See Appendix A of RFC 2373 for how to create an EUI-64 Interface Identifier. The only problem with this approach that I see is that if you remove that interface (that is it was on a card not on your motherboard) then it goes away. Perhaps generating this and storing it, no matter what the future network configuration of the system is, is the right way to go. Best, George