Comment # 9 on bug 1228728 from Björn Bidar

(In reply to Jiri Slaby from comment #8)
> (In reply to Jan Engelhardt from comment #7)
> > systemd: stop using sbin
> > me: you know what, I'm going to use it even harder
> 
> Exactly. They _always_ know what is the best for me. Mostly, they are wrong. 
> 
> > I'm with Thorsten on this one, less clutter please. About 17% of the stuff
> > in /usr/sbin is daemons anyway which could eventually move to /usr/libexec.
> 
> OTOH there are entries like sysctl (checking mostly kernel.core_pattern) and
> mkfs/fsck (creating/checking a FS in a file) which I have no idea why are
> not accessible to a user. Every time, I have to prepend /sbin/ to call them.

Can regular users touch block devices? I could see why a user would require
sysctl's but there's nothing they can do about it unless they also have root
access which negates the reason to call sysctls as user.

Some tools work as regular users but require root to be fully working.

> Then, there are utils which already have to have:
> /usr/bin/tcpdump -> ../sbin/tcpdump
> /usr/bin/ip -> ../sbin/ip
> 
> So it's all mess -- both one way and the other.

Again do this fully work as regular user?


To me this looks like Fedora enforcing their own decisions on others,
politically not a smart move imho.