Lines Matching refs:busybox

7   make                # This creates the "busybox" executable
41   PATH= ./busybox ash
43 Standalone shell mode causes busybox's built-in command shell to run
44 any built-in busybox applets directly, without looking for external
46 the only commands busybox can find are the built-in ones.
51 to the location of your busybox binary, usually /bin/busybox.
61 statically linked.  To save space, busybox can be configured with only the
82 busybox up to date.
89 behavior.  (Try "mv busybox ls" and then "./ls -l".)
91 Installing busybox consists of creating symlinks (or hardlinks) to the busybox
92 binary for each applet enabled in busybox, and making sure these symlinks are
96 "busybox.links" (created by make), which contains the list of enabled applets
99 Installing links to busybox is not always necessary.  The special applet name
100 "busybox" (or with any optional suffix, such as "busybox-static") uses the
102 "./busybox cat LICENSE".  (Running the busybox applet with no arguments gives
103 a list of all enabled applets.) The standalone shell can also call busybox
104 applets without links to busybox under other names in the filesystem.  You can
105 also configure a standalone install capability into the busybox base applet,
106 and then install such links at runtime with one of "busybox --install" (for
107 hardlinks) or "busybox --install -s" (for symlinks).
109 If you enabled the busybox shared library feature (libbusybox.so) and want
113   LD_LIBRARY_PATH=`pwd` ./busybox
123 To build out of tree, cd to an empty directory and configure busybox from there:
140 Se also the busybox FAQ, under the questions "How can I get started using
142 available from http://www.busybox.net/FAQ.html