From owner-freebsd-current Sat Dec 11 23:12:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 44B5F150CC; Sat, 11 Dec 1999 23:12:09 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id AAA63703; Sun, 12 Dec 1999 00:12:07 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA37066; Sun, 12 Dec 1999 00:12:07 -0700 (MST) Message-Id: <199912120712.AAA37066@harmony.village.org> To: Mike Smith Subject: Re: HEADSUP: wd driver will be retired! Cc: Lyndon Nerenberg , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 11 Dec 1999 17:41:25 PST." <199912120141.RAA00880@mass.cdrom.com> References: <199912120141.RAA00880@mass.cdrom.com> Date: Sun, 12 Dec 1999 00:12:07 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912120141.RAA00880@mass.cdrom.com> Mike Smith writes: : This is the usual poorly thought out argument, which fails to note that : when you lose a disk you're already screwed due by /etc/fstab and the : need to hard-mount local filesystems. No. You aren't screwed. I have a system that needs /, /var, /usr and /usr/local (all on one disk) to boot, but puts the fsck/mount of all the other file systems into the background. If one of them fails, all the others are still available. : The "right" solution is and has always been to name your disks and mount : them by name. Once devfs is a reality, we'll be able to do just this. : Until then, the problem's not really as bad as you make it out to be. I'd have to disagree with this. I was constantly getting burned by the scsi system until I started hard wiring my scsi disks. The JAZ drive I have had a period in its life when sometimes it wouldn't power on (due to a bad power connection it was later discovered), so sometimes at boot the system would see it and sometimes not. My /jaz partition would wound up being where my /big partition should be and my /big partition wouldn't be there at all when this happened. After hardwiring, /jaz was the only one affected. The same issue is there with ethernet interfaces too, btw. I have a server that has 2 single fxp cards and 4 dual fxp cards. We need to replace one of the single fxp cards with a dual one (no more slots and need another interface), but to do this will require lots of renumbering/cable shuffle, etc because ALL the interface numbers will change when we do this. I'm not convinced that the "right" solution is really "right" here. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message