From owner-freebsd-hackers Thu Jun 24 23:42:59 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 3C59914BE0 for ; Thu, 24 Jun 1999 23:42:56 -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 XAA25488; Thu, 24 Jun 1999 23:43:04 -0700 Date: Thu, 24 Jun 1999 23:41:34 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jason Thorpe Cc: freebsd-hackers@FreeBSD.ORG, tech-kern@netbsd.org Subject: Re: System unique identifier..... In-Reply-To: <199906250545.WAA20374@lestat.nas.nasa.gov> 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 On Thu, 24 Jun 1999, Jason Thorpe wrote: > On Thu, 24 Jun 1999 15:02:25 -0700 (PDT) > Matthew Jacob wrote: > > > I was talking about this on linux-kernel, but it also applies to *BSD... > > > > What're folks' motions of a settable system unique identifier, available > > prior to mountroot? This identifier has to be 64 bits or better and must > > be persistent across reboots. > > ...to be used for...? > Specifically in this case a Node WWN for fibre channel fabrics that does not depend upon an assigned WWN in any particular Fibre Channel card (multipathing might make it desirable to have a synthetic Node WWN that can also be passed to partner systems in a failover configuration). More generally a system unique identifier available early (pre mountroot) could be useful for a number of things. Why're you asking? -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message