A_brief_story_of_hier

I don't see why, and this is never justified. If the distinction is required, the mere location of the binary is probably insufficient and certainly not required.

For example, `command -V sh` now returns `/usr/bin/sh`, which is not `/bin/sh`. Among other things this means it is no longer possible to generate shebangs and have them actually work on similar systems.

Also, `dpkg -S` is now completely broken for the common case where its argument is the result of the above or `realpath`, and the two parties who are collectively responsible just say "screw you" to the other instead of fixing things.

As a result, every single package-checking script out there has to now do a dance:

* does the requested path start with /bin/ or /usr/bin/, /sbin/ or /usr/sbin/, /lib* or /usr/lib? If so, check both. This can requires significant refactoring. * Otherwise, fall back to the old code that used to work unconditionally.

(I'm only familiar with Debian's breakage but I expect most other distros have similar breakage)