[openbeosstorage] Re: ISO9660/cdrom progress
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: openbeosstorage@xxxxxxxxxxxxx
- Date: Wed, 25 Dec 2002 02:05:45 +0100 CET
Tyler Dauwalder <tyler@xxxxxxxxxxxxx> wrote:
> Thanks to some help from Marcus and Axel, I think I'm finally getting
> close to wringing some session info out of my cdrom drive. :-) I also
> have a nearly working ISO9660 fs module, and finishing it should be
> fairly straightforward. I'll post more news when I have some.
Very nice!
We should also have priorities for the file system modules (i.e. a UDF
file system should always get the disk, not the ISO-9660 file system,
if possible).
Also, how does the system deal with multi-session CDs (and the like)=3F
We might also want to have write support built-in, disks that span over
several volumes, etc.
At least we should think about every possible extension we might want
to add to that piece of code.
> It appears the the module emulator is not working quite right in
> instances where you have two (and probably more) modules of the same
> type. When testing the iso9660 fs module (alongside the bfs module),
> both modules are init'd and uninit'd initially when the list is
> created, but only the first one (bfs, in this case) is returned by
> read=5Fnext=5Fmodule=5Fname(), which then returns an error the second time
> it's called. I'll look into it more if I get sessions working.
Very nice, too :-)
Adios...
Axel.
- References:
- [openbeosstorage] ISO9660/cdrom progress
- From: Tyler Dauwalder
Other related posts:
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- » [openbeosstorage] Re: ISO9660/cdrom progress
- [openbeosstorage] ISO9660/cdrom progress
- From: Tyler Dauwalder