udhcpc: filter unwanted packets in kernel

[oweals/busybox.git] / INSTALL

diff --git a/INSTALL b/INSTALL
index 4d0a09f9afafe0caed7e916ce860dbc4c07ad4eb..a7902ab8dc4ffc20b51d65835d820589bea8df43 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -5,7 +5,7 @@ The BusyBox build process is similar to the Linux kernel build:
 
   make menuconfig     # This creates a file called ".config"
   make                # This creates the "busybox" executable
-  make install        # or make PREFIX=/path/from/root install
+  make install        # or make CONFIG_PREFIX=/path/from/root install
 
 The full list of configuration and install options is available by typing:
 
@@ -32,8 +32,10 @@ any built-in busybox applets directly, without looking for external
 programs by that name.  Supplying an empty command path (as above) means
 the only commands busybox can find are the built-in ones.
 
-(Note that the standalone shell currently requires /proc/self/exe to
-launch new applets.)
+Note that the standalone shell requires CONFIG_BUSYBOX_EXEC_PATH
+to be set appropriately, depending on whether or not /proc/self/exe is
+available or not. If you do not have /proc, then point that config option
+to the location of your busybox binary, usually /bin/busybox.
 
 Configuring Busybox:
 ====================
@@ -53,7 +55,7 @@ is run without an existing configuration, make defconfig will run first to
 create a known starting point.
 
 Other starting configurations (mostly used for testing purposes) include
-"make allbaseconfig" (enables all applets but disables all optional features),
+"make allbareconfig" (enables all applets but disables all optional features),
 "make allyesconfig" (enables absolutely everything including debug features),
 and "make randconfig" (produce a random configuration).
 
@@ -112,7 +114,7 @@ configuration step, as in:
   make O=/some/empty/directory allyesconfig
   cd /some/empty/directory
   make
-  make PREFIX=. install
+  make CONFIG_PREFIX=. install
 
 More Information:
 =================