[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Weird problem with RHEL5 isofs driver when using mkisofs -x --exclude options



On Wed, 09 Jul 2008 09:23:23 +0200, Joerg.Schilling@fokus.fraunhofer.de
(Joerg Schilling) wrote:

>Giulio Orsero <giulioo@gmail.com> wrote:
>
>> On Wed, 09 Jul 2008 01:37:03 +0200, Joerg.Schilling@fokus.fraunhofer.de
>> (Joerg Schilling) wrote:
>> [root@localhost d0]# ls -la isotest
>> total 32
>> drwxr-xr-x 4 root root 4096 Jul  9 09:02 .
>> drwxr-xr-x 4 root root 4096 Jul  9 09:02 ..
>> drwxr-xr-x 2 root root 4096 Jan  1  2008 dir1
>> drwxr-xr-x 2 root root 4096 Jan  1  2008 dir2
>> [root@localhost d0]# ls -f isotest
>> dir2  dir1  ..  .
>> [root@localhost d0]#
>
>OK, so the filesystem does not behave as expected on UNIX:
>
>If "." and ".." are delivered at all, they come first.
>
>In any case, the -find variant of the command line I send you should
>work. Did you test it?

Sorry, I hadn't seen it, here's the output:

===========
mkisofs 2.01.01a42 (i686-pc-linux-gnu) Copyright (C) 1993-1997 Eric
Youngdale (C) 1997-2008 Jörg Schilling
Setting input-charset to 'UTF-8' from locale.
Total translation table size: 0
Total rockridge attributes bytes: 653
Total directory bytes: 4096
Path table size(bytes): 34
Max brk space used 21000
177 extents written (0 MB)
 
Directory listing of /
        23 drwxr-xr-x   4    0    0       2048 Jul  9 2008 [     23 02] .
        23 drwxr-xr-x   4    0    0       2048 Jul  9 2008 [     23 02] ..
        25 drwxr-xr-x   2    0    0       2048 Jan  1 2008 [     25 02] dir1
        24 drwxr-xr-x   2    0    0       2048 Jan  1 2008 [     24 02] dir2
 
Directory listing of /dir1/
        25 drwxr-xr-x   2    0    0       2048 Jan  1 2008 [     25 02] .
        25 drwxr-xr-x   4    0    0       2048 Jul  9 2008 [     25 02] ..
 
Directory listing of /dir2/
        24 drwxr-xr-x   2    0    0       2048 Jan  1 2008 [     24 02] .
        24 drwxr-xr-x   4    0    0       2048 Jul  9 2008 [     24 02] ..
total 4
drwxr-xr-x 2 root root 2048 Jan  1  2008 dir1  <=== CORRECT
drwxr-xr-x 2 root root 2048 Jan  1  2008 dir2
=============

Now I'm a bit confused.
The "non working" iso image produced on RHEL5 has correct
permissions/timestamp if I transfer in on a RHEL3 system.

So, is this a RHEL5 general fs issue or a RHEL5 isofs issue?

Why would the method used my mkisofs matter if isoinfo show the same output?
-- 
giulioo@pobox.com


Reply to: