From owner-freebsd-arch Mon Jul 24 14:29:38 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 964EA37BED6 for ; Mon, 24 Jul 2000 14:29:34 -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 XAA07890; Mon, 24 Jul 2000 23:29:24 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: mjacob@feral.com Cc: Jack Rusher , freebsd-arch@FreeBSD.ORG Subject: Re: SANs, disks, & devfs In-reply-to: Your message of "Mon, 24 Jul 2000 14:25:32 PDT." Date: Mon, 24 Jul 2000 23:29:23 +0200 Message-ID: <7888.964474163@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Matthe w Jacob writes: >Again- I think that this and the full devfs is a usable methodology. I still >would like some feedback as to whether or not linking mount (and mt, e.g.) >with libcam so I can use device VPD info or WWNs would be just too awful for >FreeBSD. This way it can be used now, without vinum. Sounds awful to me, but I guess it depends a lot on the implementation. -- 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