From owner-freebsd-arch Tue Jul 25 13:47:54 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 80FA537B864 for ; Tue, 25 Jul 2000 13:47:50 -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 WAA14273; Tue, 25 Jul 2000 22:47:42 +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 13:37:46 PDT." Date: Tue, 25 Jul 2000 22:47:42 +0200 Message-ID: <14271.964558062@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> 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 ? > >What I want is labels. But also what I want is a property that doesn't depend >on writing anything on the device media itself. I guess my terminology is too lose here. What I had in mind were a way in which any particular physical (or logical) "storage area" (to put it on the most general footing possible) can register a number of "aliases" for their device-driver-newbus-whatever name. Ie: My /dev/ad0 could have the following "aliases": /dev/ad0 "IBM SOMETHING Serial# 4958393453" (found in ATA pages) "Scratch disk 1" (found in bsd disklabel) "/mnt/scratch" (found in UFS "last mount point") and I could use any one of these in my /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