From Fedora Project Wiki

Revision as of 19:06, 1 August 2008 by Poelstra (talk | contribs) (New page: Are there any drawbacks to putting <code>/usr/local/sbin:/usr/sbin:/sbin</code> in <code>PATH</code>? Some things (<code>/sbin/start_udev</code> is one example) will never be run by norma...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Are there any drawbacks to putting /usr/local/sbin:/usr/sbin:/sbin in PATH? Some things (/sbin/start_udev is one example) will never be run by normal users and are not used in typical system administration. These things should not be in the PATH for normal users, if it can be avoided.

Doesn't libexec already exist to contain binaries that are never run by users? Technically /usr/libexec is for binaries that are never run by humans - they're designed to be spawned by other processes. if /libexec existed, that would be a good place for something like start_udev.

Alternate approach: couldn't we just symlink commonly-used binaries into /bin or /usr/bin? Yes, but this requires editing and rebuilding dozens of RPMs and constant argument about which binaries deserve special treatment. Lots more work for very little actual improvement.

MatthiasClasen: I don't have any strong opinion on this proposal, but I have to wonder what definition of 'normal user' includes 'regularly uses ifconfig and route'... In that context, "normal user" meant "non-root user".