Comment 6 for bug 611397

I personally don't see an issue with putting all of those libs in /lib and binaries in /sbin, since they ultimately support mounting filesystems other than /.

I have to wonder if those with more experience can shed light on any hidden gotchyas there. I do see that rpc.gssd has a lot of libs in /usr:

$ ldd /usr/sbin/rpc.gssd
 linux-vdso.so.1 => (0x00007fff54eb9000)
 librpcsecgss.so.3 => /usr/lib/librpcsecgss.so.3 (0x00007f70f7992000)
 libgssglue.so.1 => /usr/lib/libgssglue.so.1 (0x00007f70f7788000)
 libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00007f70f74c3000)
 libcom_err.so.2 => /lib/libcom_err.so.2 (0x00007f70f72bf000)
 libc.so.6 => /lib/libc.so.6 (0x00007f70f6f3c000)
 libdl.so.2 => /lib/libdl.so.2 (0x00007f70f6d37000)
 libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00007f70f6b10000)
 libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0x00007f70f6908000)
 libkeyutils.so.1 => /lib/libkeyutils.so.1 (0x00007f70f6704000)
 libresolv.so.2 => /lib/libresolv.so.2 (0x00007f70f64e9000)
 libpthread.so.0 => /lib/libpthread.so.0 (0x00007f70f62cb000)
 /lib64/ld-linux-x86-64.so.2 (0x00007f70f7bc5000)