Vincent Lefevre <[EMAIL PROTECTED]> wrote:
> I've attached an archive containing a directory "dir" (all the files
> are empty, but what's important is their filename and if they are
> present or not), the corresponding ISO image obtained on Mac OS X
> with:
What happens if you mount this filesystem on Linux with Rock Ridge enabled?
> hdiutil makehybrid -o test.iso dir
>
> and a ReadMe file with the full isoinfo output with "-lJ" and "-lR".
>
> I haven't tried to mount the image (I don't know how to do that) to
> see if all the files are present with mount + ls, but with "-lR",
> there are two "BAD RRVERSION" errors and the first dot of foo.tar.bz2
> is missing. Also, all the filenames are in uppercase letters.
Thank you for the data, it confirms my asumptions!
The original Author of the Linux iso-9660 filesystem is the same person
as the original Author of mkisofs. The linux kernel seems to have inherited
the same bugs as I inherited in mkisofs......
If I mount the filesystem on Solaris, I get the following listing from the
mount point:
Gesamt 0
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200309.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200310.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200311.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200312.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200401.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200402.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200403.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200404.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200405.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200406.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200407.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200408.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200409.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200410.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200411.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200412.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200501.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200502.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200503.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200504.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200505.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200506.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200507.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200508.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200509.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200510.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200511.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200512.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200601.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:10 access_log-200602.bz2
-r-xr-xr-x 1 root sys 0 Dec 25 18:09 foo.tar.bz2
/var/adm/messages contains:
Dec 25 19:10:41 opt hsfs: [ID 196000 kern.notice] NOTICE: hsfs: Warning: file
system mounted on /mnt does not use Rock Ridge version >= 1.12:
Dec 25 19:10:41 opt hsfs: [ID 260047 kern.notice] hard linked files disabled
Dec 25 19:10:41 opt hsfs: [ID 674684 kern.notice] Due to this error, the file
system may not be correctly interpreted.
Dec 25 19:10:41 opt hsfs: [ID 532498 kern.notice] Other such errors in this
file system will be silently ignored.
This is only a hint on the fact that the filesystem follows an _outdated_
Rock Ridge standard. This is the same outdated Rock Ridge standard that
is implemented by genisoimage (Note that genisoimage is just a frozen outdated
mkisofs). The main problem with the outdated Rock Ridge version is that
hard links do not work, but the Linux kernel implementation does not support
correct hardlinks on iso-9660 either.
There is no problem with the correctness of the Rock Ridge structure. Solaris
accepts it!
Conclusion:
1) I need to fix isoinfo and mkisofs to deal correctly with the Apple
extensions.
2) The Linux kernel implementation for Rock Ridge is broken and needs
to be fixed.
Once I am done, you should upgrade to the new cdrtools release.
This will be another reason not to use the fork called "cdrkit".
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
