From owner-freebsd-chat Thu Sep 28 23:53:35 2000 Delivered-To: freebsd-chat@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id DB04237B422 for ; Thu, 28 Sep 2000 23:53:28 -0700 (PDT) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id XAA02246; Thu, 28 Sep 2000 23:50:52 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpdAAAI3aGre; Thu Sep 28 23:50:46 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id XAA13364; Thu, 28 Sep 2000 23:53:17 -0700 (MST) From: Terry Lambert Message-Id: <200009290653.XAA13364@usr08.primenet.com> Subject: Re: Ideas about network interfaces. To: res03db2@gte.net (Robert Clark) Date: Fri, 29 Sep 2000 06:53:16 +0000 (GMT) Cc: dot@dotat.at, tlambert@primenet.com, freebsd-chat@FreeBSD.ORG, ragnar@sysabend.org, res03db2@gte.net In-Reply-To: <200009290645.XAA01304@gte.net> from "Robert Clark" at Sep 28, 2000 11:45:27 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > One thing I do appreciate about the e4000 Suns, (and most of the > SBUS systems I would think), is that installing a new scsi > controller doesn't change the path to the existing devices. > > This is inherent in the hardware, and not something applicable to > the PC? The controllers are not named for their slots or for their PCI interrupt (A/B/C/D), nor for their bridge address, etc.. In an ideal world, you would expect slot; the best you can expect in a PCI workld is, I think, interrupt, then bridge, then interrupt off of bridge, then target, then LUN, then paritition, then subpartition, etc.. We don't do that. For a near approximation, you could use the "last mounted on" field of the FS's that support it to decide on mounting into the FS hierarchy, and add a field for the rest of the fstab elements, and get rid of the fstab. This won't work for things like an msdos FS, or most CDROMs, etc., which don't have a "last mounted on" field, or have an empty one. But you could envision a devfs/slice/last-mounted-on combination that would automatically "just work". For things like dd-duplicated disks on a single system, you would want to have a "dismount date" failed, and use the most recently dismounted of a pair of "/usr" partitions, as one approach. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message