[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [VCDImager Bugs/Devel] vcdimager on BSD/OS 4.3
From: |
Steven M. Schultz |
Subject: |
Re: [VCDImager Bugs/Devel] vcdimager on BSD/OS 4.3 |
Date: |
Thu, 30 Aug 2001 10:43:57 -0700 (PDT) |
Hi!
> btw, is __bsdi__ defined on every *BSD flavour?
No, only on BSD/OS. FreeBSD has __FreeBSD__ for example. I am not
sure what other systems (such as NetBSD) have - probably something
like __NetBSD__.
> I've added some lowlevel generic packet cdrom interface calls to the
> linuxcd image source driver... so bsd will get it's own cdrom image source
> driver; it won't need the libdvd wrapper...
Oh, cool! Are you using Joerg Schilling's generic scsi interface?
'libdvd' is what translates the linux CDROM ioctl calls into generic
SCSI commands for the kernel (which also works with ATAPI devices).
> > There is however one change to a .c file that deserves special mention.
> > Using 'fseek' and 'fread' to access the ISO portion of a VCD can cause
> actually in the next version all sectors will be read by ioctl()'s...
Ah, that will be nice. Tracking down that problem was the single
biggest challenge in getting vcdimager to run.
> > "-ldvd" which is a linux DVD/VCD/CD ioctl emulation library described
> a no-problem, since libdvd won't be necessary...
Will a "per OS" 'cdrom image source driver' be needed? Each system
is different in how it accesses devices. It may be necessary to
use the 'libdvd' interface as the BSD/OS 'cdrom image source driver'.
> btw, the libdvd seems like a rip-off of the linux kernel's cdrom.c...
Indeed it is! I needed to emulate the DVD/IOCTL functions so that
ioctl(fd, CDROMREADRAW2, ...) behaved the same - what better guide
than the Linux cdrom.c? :-)
> ...you can't stop development from happening from time to time... *g*
Quite true ;) For a long time I've been using a hacked version of
0.6.2 - then I decided to give 0.7.9 a try a couple evenings ago.
Thanks for the quick response - I appreciate it.
Steven