On 10/21/2010 05:11 AM, Rocky Bernstein wrote:
As the header in include/cdio/ecma_167.h suggests, the code should be
following the ECMA-167 specifications, 3rd edition, June 1997. A URL for
the PDF is given:
http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-167.pdfand
that still works.
Section 4 has information on how files are laid out. I don't see the
guarantees, you are looking for, but you should read it yourself.
then does libcdio work? it would seem from my reading that every
udf_read_block() is basically made as an offset to the start of the file.
i.e.
1) it calls offset_to_lba to find start sector and length
2) computed max # of blocks
3) calls udf_read_sectors() w/ that information
udf_read_sectors()
translated the call into a
cdio_stream_read() or cdio_read_data_sectors() call (as I'm dealing with
image files, I'll just deal with stream_read()
and cdio_read_data_sectors() seems like its just a sequential read.
so am I right to understand that libudf would (could?) fail on these
files if they are guaranteed to be sequential?
