[Unionfs] RE: ldconfig and unionfs?

[Erez Zadok]

In message <BAY108-W423D8614AA638633AA92FA96220 at phx.gbl>, John Nielsen writes:
> 
> 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.

John, are the *.so files symlinks in /mnt/serenity, or are they regular
files?

I'll try to reproduce this on my end.

Thanks,
Erez.