From owner-freebsd-hackers  Fri Jun 25  0: 1:38 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29])
	by hub.freebsd.org (Postfix) with ESMTP id 2D2D014BE0
	for <freebsd-hackers@FreeBSD.ORG>; Fri, 25 Jun 1999 00:01:32 -0700 (PDT)
	(envelope-from thorpej@lestat.nas.nasa.gov)
Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id AAA21253; Fri, 25 Jun 1999 00:01:25 -0700 (PDT)
Message-Id: <199906250701.AAA21253@lestat.nas.nasa.gov>
To: mjacob@feral.com
Cc: freebsd-hackers@FreeBSD.ORG, tech-kern@netbsd.org
Subject: Re: System unique identifier..... 
Reply-To: Jason Thorpe <thorpej@nas.nasa.gov>
From: Jason Thorpe <thorpej@nas.nasa.gov>
Date: Fri, 25 Jun 1999 00:01:25 -0700
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

On Thu, 24 Jun 1999 23:41:34 -0700 (PDT) 
 Matthew Jacob <mjacob@feral.com> wrote:

 > More generally a system unique identifier available early (pre mountroot)
 > could be useful for a number of things. Why're you asking?

The intended usage:

	(1) Could influence where it is stored.

	(2) Might be utterly useless (e.g. for software licensing,
	    especially when you have the source for the OS, and
	    can thus make it anything you want with a simple
	    kernel hack...)

        -- Jason R. Thorpe <thorpej@nas.nasa.gov>



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message