=head1 SYNTAX
- BusyBox <function> [arguments...] # or
+ busybox <applet> [arguments...] # or
- <function> [arguments...] # if symlinked
+ <applet> [arguments...] # if symlinked
=head1 DESCRIPTION
After the compile has finished, you should use 'make install' to install
BusyBox. This will install the 'bin/busybox' binary, in the target directory
-specified by PREFIX. PREFIX can be set when configuring BusyBox, or you can
-specify an alternative location at install time (i.e., with a command line
-like 'make PREFIX=/tmp/foo install'). If you enabled any applet installation
-scheme (either as symlinks or hardlinks), these will also be installed in
-the location pointed to by PREFIX.
+specified by CONFIG_PREFIX. CONFIG_PREFIX can be set when configuring BusyBox,
+or you can specify an alternative location at install time (i.e., with a
+command line like 'make CONFIG_PREFIX=/tmp/foo install'). If you enabled
+any applet installation scheme (either as symlinks or hardlinks), these will
+also be installed in the location pointed to by CONFIG_PREFIX.
=head1 USAGE
that performs the same job as more than one utility program. That means there
is just a single BusyBox binary, but that single binary acts like a large
number of utilities. This allows BusyBox to be smaller since all the built-in
-utility programs (we call them applets) can share code for many common operations.
+utility programs (we call them applets) can share code for many common
+operations.
You can also invoke BusyBox by issuing a command as an argument on the
command line. For example, entering
=head1 COMMON OPTIONS
-Most BusyBox commands support the B<--help> argument to provide a terse runtime
+Most BusyBox applets support the B<--help> argument to provide a terse runtime
description of their behavior. If the CONFIG_FEATURE_VERBOSE_USAGE option has
been enabled, more detailed usage information will also be available.
=head1 COMMANDS
-Currently defined functions include:
+Currently available applets include: