![](https://seccdn.libravatar.org/avatar/cabdbf4d350ab6a15265803acab1634d.jpg?s=120&d=mm&r=g)
On 12/23/2016 10:20 AM, Carl Symons wrote:
Highly motivating message, Rudeli.
diff -srq /bin/ /usr/bin | grep identical
Hmmmm # diff -srq /bin/ /usr/bin | grep identical | wc -l 113 so, how many of those are symlinks? # ls -l /bin | grep -e "->" | wc -l 112 So, what's the exception? Now, if as recommended, the /usr part of the file system is on the ROOTFS volume, those could be hard links. In which case they are truly redundant. It seems, superficially at lest, that this is a fob for those who don't have /usr/bin on the same FS as /bin. And given all that, if you have both /bin and /usr/bin on your SEARCH path, the why have the symlinks at all? Yes, I realise that that if there were no symlinks then the execl code would search /bin first, not find it, then search /usr/bin, but then again, at some level, the execl code, either at the user level or the kernel level, is going to find that the version found in /bin is a symlink and have to go find the version in /usr/bin by step and repeat. Or maybe its faster with a Btree-FS. Surely a script that converts symlinks into hard links if they are on the same FS isn't that difficult, and why couldn't that script be in the RPM as a post-install? -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org