^^^^^^^^^^^Bruce Dubbs wrote these words on 02/22/05 00:27 CST:
Jim Gifford wrote:
.so files belong in /usr/lib .so.version belong in /lib.
I'm not sure what you are saying here Jim. If the library file
is either referenced as a symlink or a regular file by an excutable file in /bin or /sbin, it needs to be in /lib. There should be no links from /lib to a location outside of /lib. The rule here is that the programs must be execuatable if /usr is not mounted.
So I can get a better handle on what you're trying to drive at Bruce, let's use the /bin/login program as an example.
[EMAIL PROTECTED]: ~ > ldd /bin/login linux-gate.so.1 => (0xffffe000) libmisc.so.0 => /lib/libmisc.so.0 (0x4003b000) libshadow.so.0 => /lib/libshadow.so.0 (0x4004c000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x40063000) libpam.so.0 => /lib/libpam.so.0 (0x40091000)
libpam_misc.so.0 => /lib/libpam_misc.so.0 (0x4009a000) libc.so.6 => /lib/libc.so.6 (0x4009d000) libdl.so.2 => /lib/libdl.so.2 (0x401b3000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
How does the libpam.so symlink factor into *any* requirement of the login program?
Do a ls -l /lib/libpam*
Don't you have something like:
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
The program accesses the symlink, which must be available in /lib. The link accesses the file which also must be in /lib.
-- Bruce
-- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
