From owner-freebsd-current Thu Mar 4 9:22:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.nerds4rent.com (ns2.freedomnet.com [198.240.104.10]) by hub.freebsd.org (Postfix) with ESMTP id 32F1015097 for ; Thu, 4 Mar 1999 09:22:28 -0800 (PST) (envelope-from kbyanc@freedomnet.com) Received: from tech (tech.nerds4rent.com [198.240.104.20]) by mail.nerds4rent.com (8.8.8/8.8.8/antispam) with SMTP id MAA16933 for ; Thu, 4 Mar 1999 12:37:06 -0500 (EST) X-Envelope-To: From: "Kelly Yancey" To: Subject: RE: ATAPI and ATAPI_STATIC with the new ATA* driver? Date: Thu, 4 Mar 1999 12:23:29 -0500 Message-ID: <000001be6663$b897bca0$1468f0c6@tech.freedomnet.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It's really frustrating if I add new drive (anywhere on the busses) and > > other drives change their numbers - it's good base for big troubles > > (infinite changing /etc/fstab and so on). > Fair enough. But in real life, you don't add a new drive "anywhere on > the busses". You know _exactly_ which controller you're attaching the > drive to, and you know whether the drive is the master or the slave. > This information is enough for you to figure out _exactly_ where in the > probing the drive will be "spotted" and numbered. > I'm not sure I understand what real-world frustrations people are having > here. Is this thread the product of reactionary criticism, or are there > real examples of situations in which there are serious disadvantages to > the way Soren has things working? > Ciao, > Sheldon. I think you are absolutely right. On all of our servers here, all running various versions of FreeBSD, we've been using SCSI drives for years, which as we all know have the same "problem" that ATA drives have now. The only difference is that with SCSI devices, a mechanism exists to wire-down device names to devices. The only real problem that exists with the new ATA driver is that it doesn't support the same wiring-down for ATA devices. I don't remember who suggested it a couple of days ago, but I thought it was a good idea: to simply extend the wiring-down scheme that we already have to support ATA devices too. He also suggested a more universal device name like drv0, drv1, drv2, etc rather than deliniating between whether the drive is ATA or SCSI...I also think that is a good idea as I don't see any good reason an application should care whether the drive is ATA or SCSI, as long as the functionality is provided does it matter how? Great job Soren, the new drivers are great (although DMA support would make them extra cool :) ) Kelly ~kbyanc@posi.net~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message