From owner-freebsd-arch Tue Jul 25 13: 0:15 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 D63D837B86E for ; Tue, 25 Jul 2000 13:00:12 -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 WAA13951; Tue, 25 Jul 2000 22:00:05 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: 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 12:51:01 PDT." Date: Tue, 25 Jul 2000 22:00:05 +0200 Message-ID: <13949.964555205@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthew Jacob writes: > >> 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. > >For devices that have been so labelled, yes, and that the label in question >can be written to the device media (or stored in the device). This means that >you have an import step. Not the worst thing in the world, but it does indeed >restrict usage and sharing on a SAN- you can't rewrite the 50 NT volume labels >on the SAN to find a FreeBSD identifier. Ahh, but if they are NT volumes, the are unlikely to be UFS filesystems, and in that case I'm sure we would simply adopt the NT labels, no ? Maybe the solution here is that each device and indeed partition can have multiple labels, and any one of those are good enough for /etc/fstab ? -- 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