Am 16.08.2015 um 18:57 schrieb Nico Kadel-Garcia:
It's a basic violation of the ordinary segregation between
"/bin" as
ordinary user tools" and "/sbin" as sysadmin tools to start mixing
them, and much more confusing to have the same program name in both.
And it's frankly easy to avoid. "mock", for example, should rename
"/.sbin/mock" to something else to avoid command line confusion
nonsense
./sbin/ is nowehre in the FHS
./sbin/ is not below/usr
./sbin is not protected ReadOnlyDirectories=/usr
/usr/lib/appname and /usr/libexec exists