Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=468189
--- Comment #34 from Gratien D'haese gratien.dhaese@it3.be 2009-03-28 09:54:12 EDT --- (In reply to comment #33)
- What I meant by the previous comment is that it looks strange that there is /usr/share/rear/skel/default/lib64 directory but /usr/share/rear/skel/default/usr/lib64 does not exist in this package, for example.
I did an experiment with FC9 on a x86_64 platform: - ran 'rear mkrescue' of rear-1.7.19 without modification and - once with creating an empty directory under skel/usr/lib64 and ran 'rear mkrescue' again
Boot initrd were extracted in a temporary directory to compare the file structure: [root@sloeber lib64]# ls -l /tmp/rootfs/usr total 4 lrwxrwxrwx 1 root root 6 2009-03-28 12:49 bin -> ../bin lrwxrwxrwx 1 root root 6 2009-03-28 12:49 lib -> ../lib lrwxrwxrwx 1 root root 3 2009-03-28 12:49 sbin -> bin drwxr-xr-x 4 root root 4096 2009-03-28 12:49 share [root@sloeber lib64]# ls -l /tmp/rootfs_2/usr total 8 lrwxrwxrwx 1 root root 6 2009-03-28 14:41 bin -> ../bin lrwxrwxrwx 1 root root 6 2009-03-28 14:41 lib -> ../lib drwxr-xr-x 2 root root 4096 2009-03-28 14:41 lib64 lrwxrwxrwx 1 root root 3 2009-03-28 14:41 sbin -> bin drwxr-xr-x 4 root root 4096 2009-03-28 14:41 share [root@sloeber lib64]# ls -l /tmp/rootfs_2/usr/lib64/
The /usr/lib64 directory remains empty. If you wish we could make a symlink to ../../lib64? Did a boot test with the first iso image, which went fine.