View Single Post
Old 03-07-2012, 04:00 PM   #7
knc1
Embedded Cheerleader
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,347
Karma: 5840124
Join Date: Feb 2012
Device: Too many.
Quote:
Originally Posted by geekmaster View Post
P.S. Busybox commands do not need symlinks. You can just stick "busybox" in front of busybox built-in commands (like "busybox sh").
There are two ways that busybox may be configured -
One (which does not require sym-links) does require that /proc be mounted.

The other configuration choice does require links (either symbolic or hard) but will work without /proc mounted.
This configuration option also allows you to just replace a bb link with an executable and you will get the real-executable. Also a real-executable "wins" according to the usual path rules over the bb link.

From your post, the BBs that you write about must be configured per the first choice above.
I always option my builds of BB according to the second way.

Last edited by knc1; 04-16-2012 at 06:41 AM.
knc1 is offline   Reply With Quote