From owner-freebsd-current Fri Mar 5 18:34:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles171.castles.com [208.214.165.171]) by hub.freebsd.org (Postfix) with ESMTP id 04F0F15231 for ; Fri, 5 Mar 1999 18:34:05 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA64778; Fri, 5 Mar 1999 18:19:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903060219.SAA64778@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ville-Pertti Keinonen Cc: Sheldon Hearn , current@freebsd.org Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-reply-to: Your message of "04 Mar 1999 13:05:39 +0200." <86iuchms58.fsf@not.oeno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 18:19:23 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's been like this with SCSI disks since day #1. I don't see it ever having been quite the disaster of epic proportions that you make it out to be. > When a boot fails with something like /dev/rwd2s1g: Device not configured, > how long will it take you to figure out that it was actually wd1 that > didn't probe and what is now visible as wd1 is what you used to know as > wd2? If the disks are identical, you have to look carefully at the boot > messages. If that isn't a POLA violation, what is? Talk about "bike shelter" material. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message