From owner-freebsd-hackers Fri Jun 25 16:12: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1854714D57 for ; Fri, 25 Jun 1999 16:11:57 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id QAA28558; Fri, 25 Jun 1999 16:12:06 -0700 Date: Fri, 25 Jun 1999 16:10:26 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wes Peters Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: System unique identifier..... In-Reply-To: <37740B32.82B5B268@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Matthew Jacob wrote: > > > > > > Whose BIOS NVRAM? > > > > > > The host system BIOS NVRAM. I thought we were looking for a per-host > > > ID here, right? > > > > Yes, but this kind of NVRAM isn't available on an Alpha, or a Sparc. > > On the SPARC you can put it in the OpenBoot environment. I dunno > about the Alpha. There's NVRAM and so on for a lot of machines. I'm thinking that the cleanest place to put this which would be common across all *BSD's would be: a) A base release 128 bit UUID generator. b) A step in kernel configuration that snags such a value and puts it in a place that sysctl can get at it. c) A utility that binary patches the kernel so that a change via sysctl is persistent. All of this is quite grotesque. If it was FreeBSD specific, then stuff in /boot and sysctl would be fine- but I'd like to see this be *BSD, not just FreeBSD. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message