On Thu, Nov 7, 2013 at 8:43 PM, Laurent Bercot <[email protected]> wrote: > It doesn't really matter where you place your binaries. Executing a binary > should > be done with PATH search anyway, and PATH will always contain /usr/bin and > /bin at > least. If it bothers you, there's a busybox configuration option to entirely > forget > about /usr, which is the cleaner and IMHO sensible choice. > > The only case where this matters is when you have to provide absolute > pathnames, > for instance in shebang lines. #!/bin/sh, but #!/usr/bin/perl. When you have > a > script interpreter, it's important for it to be accessible via a well-known > absolute path. > Unfortunately, when it comes to guaranteeing absolute paths, the FHS sucks.
In some cases, making /usr/[s]bin symlinks to /[s]bin deals with this problem for good: both /bin/BAR and /usr/bin/BAR are the same. (Symlinking /usr to / would do too, but may be impossible if you need other /usr/FOO directories but aren't happy with moving them to /FOO). -- vda _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
