[openbeosstorage] Re: ISO9660/cdrom progress
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: openbeosstorage@xxxxxxxxxxxxx
- Date: Tue, 25 Feb 2003 23:59:09 +0100 CET
"Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx> wrote:
> > No, I haven't analyzed it at all - but my multi-session fs is
> > really
> > "simple" in that regard: it just always using absolute addressing.
> > That works fine as long as there are not do independent ISO-9660
> > sessions on that disk, and I guess that's the case with it. Since I
> > would need to be able to differentiate between a multi-session, and
> > a
> > single session, I was just too lazy to think about it, after
> > scanning
> > through the standard :-)
> > (as it works for almost every disk)
> I wonder, if that disk is perhaps indeed standard compliant. That
> would
> at least explain, why it fails when being accessed with (non-
> standard)
> absolute addressing.
Yes, that's exactly what I think - I haven't doubted for a second that
it's my fault :-)
> > Unfortunately, it even enters KDL with that CD, IIRC - so it's
> > really
> > something that should be fixed.
> I would be interested to have a look at it. Maybe you want to bring
> it
> to the next BeGeistert=3D3F!
Funny that you mention it, because I forgot to ask it in the last mail
:)
I am looking forward to meet you there!
Adios...
Axel.
- Follow-Ups:
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Ingo Weinhold
- References:
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Ingo Weinhold
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] Re: ISO9660/cdrom progress
- From: Ingo Weinhold
- [openbeosstorage] Re: ISO9660/cdrom progress
- From: Ingo Weinhold