From owner-freebsd-arch Mon Jul 24 13:56: 5 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 8800137BCED for ; Mon, 24 Jul 2000 13:55:55 -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 WAA07680; Mon, 24 Jul 2000 22:55:45 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Jack Rusher Cc: mjacob@feral.com, freebsd-arch@FreeBSD.ORG Subject: Re: SANs, disks, & devfs In-reply-to: Your message of "Mon, 24 Jul 2000 13:51:12 PDT." <397CAC40.6E2DD4DB@integratus.com> Date: Mon, 24 Jul 2000 22:55:45 +0200 Message-ID: <7678.964472145@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <397CAC40.6E2DD4DB@integratus.com>, Jack Rusher writes: >Poul-Henning Kamp wrote: >> >> The BSD disklabel already have a field for disk-name which can be >> used for this, what we need is to collect these names as we see them >> and provide a "is this disk attached and if so where" function to >> look it up. > > How do you get around fstab entries like this: > >/dev/acd0c /cdrom cd9660 ro,noauto 0 0 > >...without some idea of a positional device entry? We will obviously have to support both media-id and positional addressing, I don't think anybody seriously thought a media-id based system would be enough on its own ? -- 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