> From: "Lucky Green" <[EMAIL PROTECTED]> > Date: Tue, 8 Oct 2002 20:35:03 -0700 > Sender: [EMAIL PROTECTED] > > Lowell wrote: > > "Lucky Green" <[EMAIL PROTECTED]> writes: > > > > > Nick wrote: > > > > > Checking /dev/cdrom for cdrom... > > > > > Testing /dev/cdrom for cooked ioctl() interface > > > > > /dev/acd0a is not a cooked ioctl CDROM. > > > > > Testing /dev/cdrom for SCSI interface > > > > > /dev/cdrom is not a SCSI device > > > > > > > > That doesn't look quite right; CDROM devices are usually > > > > accessed as /dev/acd0c in FreeBSD. > > > > Only if they're ATAPI drives. Which this poster said he had. > > He also said he was using cdparanoia, which is, as the error > > message said, specific to SCSI drives. [On Linux, ATAPI > > drives are supported by making them look like SCSI drives, so > > it sort of works with cdparanoia, but on FreeBSD ATAPI drives > > are supported directly.] > > Do you believe that the ATAPI/CAM patches at > http://www.cuivre.fr.eu.org/~thomas/atapicam/ might make cdparanoia > compatible with an ATAPI drive on FreeBSD? I guess that would mean the > patches would have to provide the "cooked ioctl" that cdparanoia wants. > > I would be willing to install -CURRENT if that will make cdparanoia > work.
You probably don't need to do this. -CURRENT is a BIG change and still likely less stable than desired. The ATAPI/CAM patches are slated to be MFCed as soon as 4.7 is released and the RELENG_4 branch is re-opened. The tree should be re-opened this week unless an unexpected problem shows up, so I would expect -STABLE to have ATAPI/COM support next week. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message