From owner-freebsd-hackers Sat Jun 26 8:39:57 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 DAF3014BE6 for ; Sat, 26 Jun 1999 08:39:55 -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 IAA30546; Sat, 26 Jun 1999 08:39:59 -0700 Date: Sat, 26 Jun 1999 08:38:09 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: justin@apple.com, tech-kern@netbsd.org, freebsd-hackers@freebsd.org Subject: Re: System unique identifier..... In-Reply-To: <199906260945.LAA98821@yedi.iaf.nl> 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 Sat, 26 Jun 1999, Wilko Bulte wrote: > As Matthew Jacob wrote ... > > > > Yes, you want the WWN to stay constant. That doesn't mean it should > > necessarily be the same physical box. Nor does it mean it should be a > > system that comes with a WWN assigned to by the manufacturer. > > Manufacturers have to register and 'get' a unique range they can assign > to their products. How do you guarantee that your homegrown WWN is > really unique? Witha a value in the top 4 bits that's not one of the currently defined authoritative values. > > > I think I'm confusing myself and people. I have a WWN. By definition it > > should be unique value. All I'm asking for is a kernel function to help me > > generate such a thing (despite what Eduardo says). > > > > > > On Fri, 25 Jun 1999, Wilko Bulte wrote: > > > > > As Matthew Jacob wrote ... > > > > > > > > > > FYI: The Compaq HSG80 Fibrechannel RAID controllers have their > > > > > WWN in NVRAM. One is supposed to get the WWN from a label on the *cabinet* > > > > > into the HSG controller. This allows for easy hardware swap in case of > > > > > hardware grief. > > > > > > > > Yes, if you want the WWN to stay constant. > > > > > > Well, you do. Especially when you are using things like zoning (like > > > that Brocade switches can do) or when the host directly ties things to > > > the wwn it talks to. E.g. for connection to Sun we use Jaycor adapters > > > that allow things like "target=foo lun=bar www="<64bitnumber>" in the > > > Solaris /kernel/drv/sd.conf file > > > > And to boot a Sun over fibre channel, you use the WWN. > > Well, we currently don't support that, but indeed that is what you would > do. Tru64 Unix does something similar. You can boot off of fibre channel now- but not using a WWN. I want to see devfs fixed and using WWWs and/or device VPD. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message