From owner-freebsd-arch Tue Jul 25 12:43: 9 2000 Delivered-To: freebsd-arch@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 60FD337B924 for ; Tue, 25 Jul 2000 12:42:57 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id VAA13765; Tue, 25 Jul 2000 21:42:22 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Justin T. Gibbs" Cc: mjacob@feral.com, freebsd-arch@FreeBSD.ORG Subject: Re: How much do we need the all-singing, all-dancing devfs? In-reply-to: Your message of "Tue, 25 Jul 2000 13:28:06 MDT." <200007251927.NAA48018@pluto.plutotech.com> Date: Tue, 25 Jul 2000 21:42:22 +0200 Message-ID: <13763.964554142@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200007251927.NAA48018@pluto.plutotech.com>, "Justin T. Gibbs" write s: >> >>But there is a fully qualified 128 bit WWN. It's type 6, and it's in page 0x83 >>of VPD info for Inquiry in SPC2. > >But not all devices are SCSI and not all SCSI devices have WWNs, so >calling the FreeBSD representation of a virtual device identifier >a WWN will lead to confusion when the identifier doesn't come from >a WWN. The CAM3 spec talks a bit about virtual device identifiers >and leaves it up to the implementer to decide what data is appropriate >to make it unique. In my mind it would make more sense to make an API to examine the disklabels (of various sorts) and pick the "FreeBSD device identifier" from there. That way all devices, SCSI, ATA, IDE, RAID, Flash and so on can be handled. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message