Matthew Burgess wrote:

> That then leaves us with the following binaries that I can't see a need
> to move from /usr/bin:
> 
> [, basename, install, test, touch
> 
> Does anyone know why we do so?  

'[' is an alias for 'test' and is only used by some shells that don't
have them set as builtin.  They *might* be useful for some boot scripts,
even though we don't use them.  basename and touch fall into the same
category.

A quick check of a RH9 system shows [, install, and test in /usr/bin;
touch and basename are in /bin.

The movement of 'install' even forces us
> to symlink it back to /usr/bin for so called FHS compliance.  Searching
> the FHS I can't see where it mandates the location of 'install'.
> 
> Now to get to the real crux of what caused all this in the first place!
> 
> The udev testsuite assumes that 'test' appears in /usr/bin, not in
> '/bin', causing one of the tests to fail.  I committed a change to the
> book today that simply replaced /usr/bin/test with /bin/test, then sent
> a query upstream.
> 
> Kay Sievers explained that udev uses execv() to invoke the PROGRAM
> argument specified in its rules.  This means that a 'real binary',
> rather than the shell builtin, will be run.  Additionally, it means that
> $PATH won't be respected, so unfortunately just running 'test' won't
> work.  The ideal solution would be to figure out a way of getting the
> test/udev-test.pl script to figure out whether it should call
> /usr/bin/test or /bin/test.  However, I'm only going to invest time in
> this if someone can convince me of why we *need* to move 'test' and '['
> to /bin.

>From the above, test should stay in /usr/bin for sure.  [ is a symlink
to test and should also be in /usr/bin.  I see no reason why install
should not be in /usr/bin.

basename could be used, for instance, in customization script for dhcp
and touch could be used for file locking.  For these reasons, I'd put
these in /bin.

  -- Bruce
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to