From owner-freebsd-arch Thu Jul 27 18:47:27 2000 Delivered-To: freebsd-arch@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 55EC537C1AD; Thu, 27 Jul 2000 18:47:15 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id SAA07548; Thu, 27 Jul 2000 18:47:09 -0700 Date: Thu, 27 Jul 2000 18:47:13 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Adrian Chadd Cc: freebsd-arch@FreeBSD.ORG Subject: Re: How much do we need the all-singing, all-dancing devfs? In-Reply-To: <20000727094015.B71137@ywing.creative.net.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Matt - if I understand your initial idea right, all you wanted was a way > to map a fibrechannel disk label to a name in a devfs, so that when the > underlying device shifted 'address', you would still be able to reference > it without difficulty? Was there anything else ? No- I want to map a *device*- I don't *particularly* care what it's name is (the thing put in /etc/fstab or handed to 'mt')- but I do not necessarily want to have to write to it (for a label) to address it. I can guarantee that the address won't shift while the system is running. The other aspect of this is that these are unique names. This makes High Availability device management a *snap*. It's WWNXXXXX on all systems on the same fabric. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message