The case for the /usr merge

> 'Binaries in /bin are often not even statically linked, or at least depend on libs inside /usr/lib.'

JFTR On my Debian stable system:
$ ls -1 /bin | wc -l
104
$ ls -1 /bin | xargs -i ldd {} | grep /usr
/bin/ping6
libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0x00007f88fc791000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f88fc014000)

$ ls -1 /sbin| wc -l
182
$ ls -1 /sbin | xargs -i sh -c 'echo {}; ldd {}' | grep /usr -B10
fsck.cramfs
libz.so.1 => /usr/lib/libz.so.1 (0x00007f48dc0a2000)
mkfs.cramfs
libz.so.1 => /usr/lib/libz.so.1 (0x00007f478f0cb000)
mkfs.ntfs
libntfs.so.10 => /usr/lib/libntfs.so.10 (0x00007f4208125000)
mount.ntfs-fuse
libntfs.so.10 => /usr/lib/libntfs.so.10 (0x00007f02a6a86000)
libfuse.so.2 => /usr/lib/libfuse.so.2 (0x00007f02a6851000)
nfnl_osf
libnfnetlink.so.0 => /usr/lib/libnfnetlink.so.0 (0x00007f1af01b8000)
umount.udisks
libdbus-glib-1.so.2 => /usr/lib/libdbus-glib-1.so.2 (0x00007fc7b1575000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00007fc7b1111000)
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0x00007fc7b068f000)

Not that bad, isn't it?