[Unionfs] RE: ldconfig and unionfs?

[John Nielsen]

Hi,

Thank you for getting back to me.

Oh, I know that this warning is harmless. The only reason I brought it to your attention was because this only happens when unionfs is involved.

I ran the ls -al command from within a chroot jail:

root:/# ls -la /usr/lib/libboost_unit_test_framework-gcc42-mt-1_34_1.so.1.34.1
-rwxr-xr-x 2 root root 253068 Feb 17 23:03 /usr/lib/libboost_unit_test_framework-gcc42-mt-1_34_1.so.1.34.1

It is clearly not a symlink.

In the below two examples, /root/pkg and /root/union are just two empty folders. /mnt/serenity is a second distribution I chroot to.

Doing the following will provoke the warning:
mount -t unionfs -o dirs=/root/pkg:/mnt/serenity=ro unionfs /root/union
chroot /root/union ldconfig

While this will not:
chroot /mnt/serenity ldconfig

The two chroot commands are contextually identical. Ldconfig only thinks that these libraries are supposed to be symlinks when running on a unionfs filesystem.

Kind regards,

John Nielsen


----------------------------------------
> From: fapg-unionfs at eurotux.com
> To: unionfs at mail.fsl.cs.sunysb.edu
> Subject: Re: [Unionfs] RE: ldconfig and unionfs?
> Date: Mon, 18 Feb 2008 19:51:32 +0000
> CC: junx_dk at hotmail.com; unionfs at fsl.cs.sunysb.edu
> 
> Hi,
> 
>  The problem that you have is:
> 
>>> ldconfig: /usr/lib/libboost_unit_test_framework-gcc42-mt-1_34_1.so.1.34.1
>>> is not a symbolic link
> 
> If so, this has nothing to do with unionfs or *fs. This refer that the 
> file  /usr/lib/libboost_unit_test_framework-gcc42-mt-1_34_1.so.1.34.1 is not 
> a symbolic link and is just a warning.
> 
>  Can you 
> ls -la /usr/lib/libboost_unit_test_framework-gcc42-mt-1_34_1.so.1.34.1? 
> 
> Can you send all comands  to reproduce this?
> 
> Regards,
> Fernando Gomes
_________________________________________________________________
Få 30 nye Fun Family emoticons til Messenger – helt gratis 
http://emoticons.msn.com/da-dk/default.html