Aubin Paul wrote:

When you said "it will require more work", I just wanted to know if it was developer work, or end user work...

Ah! Developer work.

The main reason you might have problems with that, is that we have to
use Linux ioctl's to identify the media; so if there are BSD
equivelants for those, we can add them.

i.e.
CDROM_DRIVE_STATUS=0x5326
CDSL_CURRENT=( (int ) ( ~ 0 >> 1 ) )
CDS_DISC_OK=4
CDROM_DISC_STATUS=0x5327
CDS_AUDIO=100
CDS_MIXED=105
CDROM_SELECT_SPEED=0x5322

Those are the Linux IOCTL's for certain types of CDs. They're taken
from cdrom.py (in Python) which may also exist for the BSDs; as for
the audio CDs, we have to read the TOC from the drive so we can do a
CD lookup; this is done via a C Python module; it would also need an
equivelant.

I saw those, and they're very likely different on FreeBSD. However, it looks like the python-2.3 port does not install cdrom.py. Looking at the python sources, the lib/plat-freebsd* directories do not have cdrom.py in them, either. That doesn't look too well.

If there is a CDROM.py for FreeBSD, is should also have an ioctl for
eject; under linux it's an ioctl to '0x5309'

If I can find one, I'll use it. Until now, I simply used "cdcontrol -f <device> eject" on FreeBSD where Linux uses "eject".

Lars
--
Lars Eggert <[EMAIL PROTECTED]>           USC Information Sciences Institute

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature



Reply via email to