Same comand names in /usr/bin and /usr/sbin

[Nico Kadel-Garcia]

On Sun, Aug 16, 2015 at 6:24 PM, Nico Kadel-Garcia <nkadel at gmail.com> wrote:
> On Sun, Aug 16, 2015 at 2:31 PM, Reindl Harald <h.reindl at thelounge.net> wrote:
>>
>> 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
>
> /sbin isn't a separate filesystem, it is a subdirectory of "/", and
> it's explicitly mentioned at
> http://www.pathname.com/fhs/2.2/fhs-3.14.html as requiring copies or
> symlinks to certain specific, long-stable program names. Let me quote
> that document:

Ahhh, I am sorry, I may have contributed to the confusion by mistyping
"/sbin" as ""/.sbin". I'm on a new email interface, and am having some
difficulty with "overwriting" as opposed to my preferred default
"insertion" for editing. But that was my own fault.