sarge /[s]bin/* binaries linked against /usr
Hello,
On an uptodate pre-sarge box, the following shows some binaries linked
with libraries under /usr. Those binaries might (didn't test) fail when
/usr is not mounted.
Is there a policy against this ? Should I feel bugs ?
Hmmm,
/bin/lspci, /bin/setpci, /sbin/mount.smb, /sbin/mount.smbfs, and
/sbin/rmt are symlinks toward /usr. Any good reason not to have this
symlinks directly under /usr/[s]bin ?
@+,
Fab
$ ldd /bin/* | grep -C2 /usr
/bin/discover:
libdiscover.so.2 => /lib/libdiscover.so.2 (0x40030000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x4003c000)
libcurl.so.2 => /usr/lib/libcurl.so.2 (0x4005c000)
libssl.so.0.9.7 => /usr/lib/i686/cmov/libssl.so.0.9.7 (0x4008a000)
libcrypto.so.0.9.7 => /usr/lib/i686/cmov/libcrypto.so.0.9.7
(0x400bb000)
libdl.so.2 => /lib/libdl.so.2 (0x401b8000)
libz.so.1 => /usr/lib/libz.so.1 (0x401bb000)
libc.so.6 => /lib/libc.so.6 (0x401cd000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
--
libattr.so.1 => /lib/libattr.so.1 (0x401ce000)
/bin/lspci:
libpci.so.2 => /usr/lib/libpci.so.2 (0x40030000)
libc.so.6 => /lib/libc.so.6 (0x40038000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
/bin/lzop:
liblzo.so.1 => /usr/lib/liblzo.so.1 (0x40030000)
libc.so.6 => /lib/libc.so.6 (0x4004d000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
--
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
/bin/setpci:
libpci.so.2 => /usr/lib/libpci.so.2 (0x40030000)
libc.so.6 => /lib/libc.so.6 (0x40038000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
$ ldd /sbin/* | grep -C2 /usr
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
/sbin/fsck.cramfs:
libz.so.1 => /usr/lib/libz.so.1 (0x40030000)
libc.so.6 => /lib/libc.so.6 (0x40042000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
--
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
/sbin/mkfs.cramfs:
libz.so.1 => /usr/lib/libz.so.1 (0x40030000)
libc.so.6 => /lib/libc.so.6 (0x40042000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
--
libnsl.so.1 => /lib/libnsl.so.1 (0x4006f000)
libdl.so.2 => /lib/libdl.so.2 (0x40085000)
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x40088000)
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x4009d000)
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x40106000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x40128000)
libldap.so.2 => /usr/lib/libldap.so.2 (0x4012b000)
liblber.so.2 => /usr/lib/liblber.so.2 (0x40160000)
libc.so.6 => /lib/libc.so.6 (0x4016d000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x402a0000)
libgnutls.so.11 => /usr/lib/libgnutls.so.11 (0x402b5000)
libtasn1.so.2 => /usr/lib/libtasn1.so.2 (0x4031b000)
libgcrypt.so.11 => /usr/lib/libgcrypt.so.11 (0x4032c000)
libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x40379000)
libz.so.1 => /usr/lib/libz.so.1 (0x4037d000)
/sbin/mount.smbfs:
libcrypt.so.1 => /lib/libcrypt.so.1 (0x40030000)
--
libnsl.so.1 => /lib/libnsl.so.1 (0x4006f000)
libdl.so.2 => /lib/libdl.so.2 (0x40085000)
libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0x40088000)
libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x4009d000)
libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x40106000)
libcom_err.so.2 => /lib/libcom_err.so.2 (0x40128000)
libldap.so.2 => /usr/lib/libldap.so.2 (0x4012b000)
liblber.so.2 => /usr/lib/liblber.so.2 (0x40160000)
libc.so.6 => /lib/libc.so.6 (0x4016d000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x402a0000)
libgnutls.so.11 => /usr/lib/libgnutls.so.11 (0x402b5000)
libtasn1.so.2 => /usr/lib/libtasn1.so.2 (0x4031b000)
libgcrypt.so.11 => /usr/lib/libgcrypt.so.11 (0x4032c000)
libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x40379000)
libz.so.1 => /usr/lib/libz.so.1 (0x4037d000)
/sbin/nameif:
libc.so.6 => /lib/libc.so.6 (0x40030000)
Reply to: