ldd /lib32/libnss_ldap-2.5.so linux-gate.so.1 => (0xffffe000) libldap-2.3.so.0 => /usr/lib32/libldap-2.3.so.0 (0xf7f2d000) liblber-2.3.so.0 => /usr/lib32/liblber-2.3.so.0 (0xf7f20000) libresolv.so.2 => /lib32/libresolv.so.2 (0xf7f0c000) libc.so.6 => /lib32/libc.so.6 (0xf7da3000) libssl.so.0.9.8 => /usr/lib32/libssl.so.0.9.8 (0xf7d5e000) libcrypto.so.0.9.8 => /usr/lib32/libcrypto.so.0.9.8 (0xf7c3e000) /lib/ld-linux.so.2 (0x49111000) libkrb5.so.3 => /usr/lib32/libkrb5.so.3 (0xf7bbf000) libk5crypto.so.3 => /usr/lib32/libk5crypto.so.3 (0xf7b99000) libdl.so.2 => /lib32/libdl.so.2 (0xf7b95000) libcom_err.so.2 => /lib32/libcom_err.so.2 (0xf7b90000) libkrb5support.so.0 => /usr/lib32/libkrb5support.so.0 (0xf7b87000) so 32-bit applications depending on /lib32/libnss_ldap-2.5.so fail to start if /usr is on a separate device and is not currently mounted (for example during boot). Reproducible: Always
ldd /lib32/libusbpp.so linux-gate.so.1 => (0xffffe000) libusb-0.1.so.4 => /lib32/libusb-0.1.so.4 (0xf7fe2000) libstdc++.so.6 => /usr/lib/gcc/x86_64-pc-linux-gnu/4.3.2/32/libstdc++.so.6 (0xf7ec3000) libm.so.6 => /lib32/libm.so.6 (0xf7e9c000) libc.so.6 => /lib32/libc.so.6 (0xf7d33000) libgcc_s.so.1 => /lib32/libgcc_s.so.1 (0xf7d24000) /lib/ld-linux.so.2 (0x49111000) The same applies to /lib32/libusbpp.so, too.
This was raised with the core nss_ldap itself previously, however base-system (vapier) explicitly rejected bloating / by 2.1MiB that would happen if ssl and ldap were moved there. Simple solution: don't start any apps needing nss_ldap until /usr is available. Really, you shouldn't be starting them anyway before /usr is up, since nss_ldap needs an LDAP server, which is either remote or locally on /usr.
