This is very likely a CENTOS5 (RHEL5) isofs driver issue, but since it's very weird I thought to ask here whether someone can reproduce it just to be sure this is not a misconfiguration/error on my part.
Problem: dirs on which an mkisofs exclusion is made show with wrong permissions/timestamp when isofs driver load the iso image. Steps to reproduce (I did this as root just to be sure): # uname -r 2.6.18-92.1.6.el5 # mkisofs -version mkisofs 2.01 (cpu-pc-linux-gnu) (I tried stock 2.01.01a42 with no change) ===== script ===== #!/bin/sh umask 022 rm -rf ./isotest mkdir -p ./isotest/dir1 ./isotest/dir2 ./loop_mount touch -t 200801010000 ./isotest/dir1 ./isotest/dir2 mkisofs -R -o test.iso -x 'isotest/dir1/*' isotest isoinfo -lR -i test.iso sudo mount -o loop test.iso ./loop_mount ls -l loop_mount sudo umount ./loop_mount ========== What I get: INFO: UTF-8 character encoding detected by locale settings. Assuming UTF-8 encoded filenames on source filesystem, use -input-charset to override. Unknown file type (unallocated) isotest/.. - ignoring and continuing. Total translation table size: 0 Total rockridge attributes bytes: 589 Total directory bytes: 4562 Path table size(bytes): 34 Max brk space used 0 177 extents written (0 MB) Directory listing of / drwxr-xr-x 4 0 0 2048 Jul 8 2008 [ 23 02] . ?--------- 0 0 0 2048 Jul 8 2008 [ 23 02] .. drwxr-xr-x 2 0 0 2048 Jan 1 2008 [ 24 02] dir1 drwxr-xr-x 2 0 0 2048 Jan 1 2008 [ 25 02] dir2 Directory listing of /dir1/ dr-xr-xr-x 2 0 0 2048 Jul 8 2008 [ 24 02] . ?--------- 4 0 0 2048 Jul 8 2008 [ 24 02] .. Directory listing of /dir2/ drwxr-xr-x 2 0 0 2048 Jan 1 2008 [ 25 02] . drwxr-xr-x 4 0 0 2048 Jul 8 2008 [ 23 02] .. total 4 dr-xr-xr-x 2 root root 2048 Jul 8 20:39 dir1 <==== WRONG PERMS/TIME drwxr-xr-x 2 root root 2048 Jan 1 2008 dir2 What I'd expect: That "dir1" would show with proper permissions and timestamp, just like "dir2" Note: - isoinfo shows correct info - If I mount the very same iso image on a system with stock 2.4.33 kernel and isofs driver, the info is correct. - I tried using mkisofs 2.01.01a42, no change. However, I'd expect that the mkisofs exclusion would have no effect on final image since dir1 is empty, but evidently this is not the case. Thanks -- [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]