Make sure we have a show_usage function prototype

[oweals/busybox.git] / README

diff --git a/README b/README
index 4fbc763803bb2f79bea7af9c2f8d563ad1e3e6e7..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,12 +34,13 @@ 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:
 
-   glibc-2.0.x, glibc-2.1.x, Linux-libc5, uClibc.  People are looking at
-   newlib and diet-libc, but consider them unsupported, untested, or worse.
+   glibc-2.0.x, glibc-2.1.x, glibc-2.2.x, Linux-libc5, uClibc.  People
+   are looking at newlib and diet-libc, but consider them unsupported,
+   untested, or worse.
 
 Supported kernels:
 
@@ -82,7 +82,7 @@ top of ash.c as well, so check those out if you want to tweak things.
 Getting help:
 
 When you find you need help, you can check out the BusyBox mailing list
-archives at http://oss.lineo.com/lists/busybox/ or even join
+archives at http://busybox.net/lists/busybox/ or even join
 the mailing list if you are interested.
 
 ----------------
@@ -90,12 +90,12 @@ the mailing list if you are interested.
 Bugs:
 
 If you find bugs, please submit a bug report.  Full instructions on how to
-report a bug are found at http://bugs.lineo.com/Reporting.html.
+report a bug are found at http://bugs.busybox.net/Reporting.html.
 
 For the impatient: To submit a bug, simply send an email describing the problem
-to submit@bugs.lineo.com.  Bug reports should look something like this:
+to submit@bugs.busybox.net.  Bug reports should look something like this:
 
-    To: submit@bugs.lineo.com
+    To: submit@bugs.busybox.net
     From: diligent@testing.linux.org
     Subject: /bin/true doesn't work
 
@@ -122,21 +122,22 @@ understanding.
 
 FTP:
 
-Source for the latest released version can always be downloaded from 
-    ftp://ftp.lineo.com/pub/busybox. 
+Source for the latest released version, as well as daily snapshots, can always 
+be downloaded from 
+    http://busybox.net/downloads/
 
 ----------------
 
 CVS:
 
 BusyBox now has its own publicly browsable CVS tree at:
-    http://oss.lineo.com/cgi-bin/cvsweb/busybox/
+    http://busybox.net/cgi-bin/cvsweb/busybox/
 
 Anonymous CVS access is available.  For instructions, check out:
-    http://oss.lineo.com/cvs_anon.html
+    http://busybox.net/cvs_anon.html
 
 For those that are actively contributing there is even CVS write access:
-    http://oss.lineo.com/cvs_write.html
+    http://busybox.net/cvs_write.html
 
 ----------------