On Sat, 2002-11-09 at 14:09, Marcus Brinkmann wrote: > Certainly not. There is no point in sbin if it is i every users path. > It is our believe that the distinction between sbin and bin is useful. Who is 'our' in this case. The FHS committee? My point was that if we can reasonably show that on a GNU/Hurd system that most (say 90-95%?) of the commands in sbin would be reasonable for a power user to use there is probably value in just having that in the general users path. You don't want namespace collisions between bin and sbin anyway, so there shouldn't be too much of a worry. It's not like you're protecting newbie's since I would expect them to not ever see the command line anyway. Tks, Jeff Bailey -- When you get to the heart, use a knife and fork. - From instructions on how to eat an artichoke.
Attachment:
signature.asc
Description: This is a digitally signed message part