Make sure we have a show_usage function prototype

[oweals/busybox.git] / README

diff --git a/README b/README
index aeff7dc3e0b4b700e4c8963be461ba111d5534a2..5037992107fe4e86b2d4e479a1e9c1d4c69a4ed2 100644 (file)
--- a/README
+++ b/README
@@ -18,9 +18,8 @@ it also makes an excellent environment for any small or embedded system.
 
 As of version 0.20 there is now a version number. : ) Also as of version 0.20,
 BusyBox is now modularized to easily allow you to build only the components you
-need, thereby reducing binary size. To turn off unwanted BusyBox components,
-simply edit the file "Config.h" and comment out the components you do not need
-using C++ style (//) comments.
+need, thereby reducing binary size. Run 'make config' or 'make menuconfig'
+for select the functionality that you wish to enable.
 
 After the build is complete, a busybox.links file is generated.  This is
 used by 'make install' to create symlinks to the busybox binary for all
@@ -35,7 +34,7 @@ Supported architectures:
    Busybox in general will build on any architecture supported by gcc.  It has
    a few specialized features added for __sparc__ and __alpha__.  insmod
    functionality is currently limited to x86, ARM, SH3/4, powerpc, m68k, 
-   and MIPS.
+   MIPS, and v850e.
 
 Supported libcs: