Nicolas Williams wrote: > On Thu, Dec 13, 2007 at 03:43:52PM -0600, Mike Gerdts wrote: >> On Dec 13, 2007 3:08 PM, Joseph Kowalski <jek3 at sun.com> wrote: >>> (Nit, I just noticed, and I have this right, (1m) should *not* be in the >>> list for /usr/bin, right?) >> Sigh. You would think so (I did). Do this with your legacy man(1). >> >> cd /usr/bin >> man -l * 2>/dev/null | grep 1m >> >> Based upon what I see in there, I wonder why /usr/sbin even exists. >> It seems as though all it does is hide ping(1M) from those that aren't >> worthy. Surely the typical person doesn't run savecore or wracct. > > I think the situation with /usr/sbin is a bit confused and confusing. > Many things in /usr/sbin probably belong in /usr/bin. I think one > criterion for deciding whether something belongs in /usr/bin or > /usr/sbin should be how much damage someone with the right RBAC profiles > might do when executing some admin command in a regular shell, or in a > profile shell. Certainly all the *stat(1M) commands belong in /usr/bin. > > Nico
Have fought one bruising ARC case about what belongs in /usr/sbin already, I'm loathe to jump in again... however, it's pretty obvious that commands that are useful w/o privilege don't belong in /usr/sbin, since adding /usr/sbin to your path to pickup those useful commands means that any perceived safety advantage is lost. - Bart -- Bart Smaalders Solaris Kernel Performance barts at cyber.eng.sun.com http://blogs.sun.com/barts
