Re: /sbin link to /bin?

[Jacob H-A <jsha@newview.org>]

In the words of Roland McGrath:
> Conversely, the /bin vs /sbin distinction is purely about avoiding
> inconvenience and/or confusion for the normal user.  The sole thing
> accomplished by putting some things in /sbin rather than /bin is that if
> you don't put /sbin in your path, you won't see those things.

Since each individual user can set up translators him or herself,
it should be possible for the contents of /bin to be different from
user to user.  An average user would only have the standard binaries
shadowed onto /bin, while root would also have the system binaries
there.  This is also nice in that if a user wants to run his
own binaries, he does not have to put another directory in his path--
he simply shadows all his binaries onto /bin.  Optimally, you should
only need /bin in your path, and every binary should be findable
there.  Obviously, this would be an administrative nightmare, except
for the fact that the files actually reside in a more manageable
structure, such as /package/foo/<...>.

>From a practical standpoint, as you said, most Hurd users are likely
to have /sbin in their paths anyways, so does it really matter if
/sbin is separate?

-- 
Jacob H-A
#!/bin/sh
cd;Q=`printf "\047"`;q(){ printf "%s\n" "$1$Q$1$Q>>.signature";};q '#!/bin/sh
cd;Q=`printf "\047"`;q(){ printf "%s\n" "$1$Q$1$Q>>.signature";};q '>>.signature