[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: hurd does NOT need /hurd



On Mon, May 20, 2002 at 02:46:34AM +0200, Marcus Brinkmann wrote:
> You are looking at completely the wrong properties.  The issue is not at all
> if a file is a binary, a text file, a picture or a marshmallow from outer
> space.  Here are a few hints that should bring you on the right track:
> 
> /bin:  Executables that should be in the user's (including the superuser's) PATH.
> /sbin: Executables that should be in the superuser's PATH, but not in the
>        PATH of other user's.

> /libexec: executables that should not be in any user's path and that are
>           started indirectly by other programs for their own purpose.
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> /hurd: executables that can do something useful with the bootstrap port to
>        attach themself as Hurd servers to the file system, that should not
>        be in any user's PATH, and are started indirectly by settrans or
                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>        the parent filesystem on the explicit request of the user.
         ^^^^^^^^^^^^^^^^^^^^^

Kindly explain the difference between the indicated phrases.

> Forget any argument about what can be started as a program.

Stop making it.

-- 
  .''`.  ** Debian GNU/Linux ** | Andrew Suffield
 : :' :  http://www.debian.org/ | Dept. of Computing,
 `. `'                          | Imperial College,
   `-             -><-          | London, UK

Attachment: pgpD1m7qEKfuI.pgp
Description: PGP signature


Reply to: