Re: xorriso: listing files+offsets in an ISO9660 image w/o RockRidge
Hi,
> Interestingly 1.4.7 can read one more of these ISOs, leaving 19 bad.
Was that already with -read_fs "norock" ?
If so: Do you still see the error message
"Damaged RR/SUSP information."
?
> With 1.3.2 and this ISO in particular, it said
> libisofs: SORRY : Mandatory Rock Ridge PX entry is not present or it
> contains invalid values.
The error message still exists in 1.4.7. Somehow it must have avoided it.
> with 1.4.7, I get a few warnings
> libisofs: WARNING : Sum of resolved file name collisions: 159
Name collisions should not occur in any filesystem tree.
There is a limit of 255 characters per path component. Longer names get
truncated and could then collide. But that's very unlikely because the
truncated names contain a string with the MD5 of the untruncated name.
Are there preceeding warnings of form
File name collision resolved with %s . Now: %s
?
The path and file name inserted into "%s" would be of interest.
> Boot record : (system area only) , not-recognized APM
That's not a warning but a status summary:
"(system area only)" = No El Torito boot record is present.
"not-recognized" = none of the known hard disk boot sectors was recognized.
"APM" = an Apple Partition Map was found.
You might get more details about the APM with
xorriso -indev ... -report_system_area plain
> System id: APPLE COMPUTER, INC., TYPE: 0002
> Volume id: IPHOTOARCHIV_240206
Might "240206" be a date stamp ? (24 Feb 2006 ?)
Have a nice day :)
Thomas
Reply to: