From owner-freebsd-current Fri Mar 5 23:16: 3 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 2A96B14D34 for ; Fri, 5 Mar 1999 23:15:55 -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 XAA66909; Fri, 5 Mar 1999 23:10:18 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903060710.XAA66909@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" Cc: Kelly Yancey , current@freebsd.org Subject: Re: ATAPI and ATAPI_STATIC with the new ATA* driver? In-reply-to: Your message of "Fri, 05 Mar 1999 19:13:43 +0900." <36DFAE57.60DFD4D1@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Mar 1999 23:10:17 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Kelly Yancey wrote: > > > > 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? > > The boot code might be distressed... :-) Not as long as the ordering matched the BIOS ordering. The boot code would love it. -- \\ 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