On Tue, Feb 22, 2005 at 12:48:27AM -0600, Bruce Dubbs wrote: > > lrwxrwxrwx 1 root root 14 /lib/libpam.so.0-> libpam.so.0.78 > -rwxr-xr-x 1 root root 30448 /lib/libpam.so.0.78
I think this is where the confusion is. .so symlinks != .so.version symlinks. .so.version is what ldd references whereas from what I understand a program that needs the lib at compile time looks for just the plain .so unless a version-dependent check is required by the program being built, in which case it will likely look for .so.version. If the above understanding is correct, then .so.version should be in /lib if required at boot, and all .so links should be in /usr/lib because they are *only* used at compile time. With that said, though, it seems bad for organization to put a real lib in /lib only to obfuscate things by putting links to it in /usr/lib. I don't know why it is done that way except to keep /lib small, but if a lib is in /lib, so should *all* it's links be, IMO. Again, this is only for organization. I just don't see the benefit of splitting them up and causing us to have 2 dirs to work with for the same library. -- Archaic Want control, education, and security from your operating system? Hardened Linux From Scratch http://www.linuxfromscratch.org/hlfs -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
