A few more updates

Changelog

@@ -51,6 +51,7 @@
 	* Matt Kraai -- logger now logs all arguments, not just the first
 	* Gennady Feldman -- syslogd no longer logs to localhost if compiled
 	    for remote logging...
+	* Richard June <rjune@ims1.imagestream-is.com> -- support for 'gzip -d'
 	* various artists -- Other good stuff that I forgot to document.
 
 

README

@@ -11,17 +11,17 @@ the expected functionality and behave very much like their GNU counterparts.
 BusyBox has been written with size-optimization and limited resources in mind.
 It is also extremely modular so you can easily include or exclude commands (or
 features) at compile time. This makes it easy to customize your embedded
-systems. To create a working system, just add a kernel, a shell (such as ash),
+systems. To create a working system, just add a kernel and an editor (such as
-and an editor (such as elvis-tiny or ae).
+e3 (http://www.sax.de/~adlibiti) or elvis-tiny).
 
 BusyBox was originally written to support the Debian Rescue/Install disks, but
 it also makes an excellent environment for any small or embedded system.
 
-As of version 0.20 there is a version number. : ) Also as of version 0.20,
+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
+simply edit the file "Config.h" and comment out the components you do not need
-need using C++ style (//) comments.
+using C++ style (//) comments.
 
 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
@@ -30,24 +30,57 @@ forest into `pwd`/_install unless you have defined the PREFIX environment
 variable (i.e., make PREFIX="/tmp/foo" install)
 
 ----------------
+
 Getting help:
+
 When you find you need help, you can check out the BusyBox mailing list
 archives at http://opensource.lineo.com/lists/busybox/ or even join
 the mailing list if you are interested.
 
 ----------------
+
 Bugs:
-If you find bugs, follow the instructions at http://bugs.lineo.com/Reporting.html
+
-and submit a bug report.  This way, we can be sure nothing falls through the 
+If you find bugs, please submit a bug report.  Full instructions on how to
-cracks...
+report a bug are found at http://bugs.lineo.com/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.lineo.com
+    From: diligent@testing.linux.org
+    Subject: /bin/true doesn't work
+
+    Package: busybox
+    Version: 0.48
+
+    When I invoke '/bin/true' it doesn't work.  I expected it to return 
+    a "0" but it returned a "1" instead.  Here is the transcript:
+	$ /bin/true ; echo $?
+	1
+    With GNU /bin/true, I get the following output:
+	$ /bin/true ; echo $?
+	0
+    I am using Debian 2.2r2, kernel version 2.2.18, and the latest
+    uClibc from CVS.  Thanks for the wonderful program!
+	-Diligent
+
+Note the careful description and use of examples showing not only what BusyBox
+does, but also a counter example showing what an equivalent GNU app does.  Bug
+reports lacking such detail may take a _long_ time to be fixed...  Thanks for
+understanding.
 
 ----------------
+
 FTP:
+
 Source for the latest released version can always be downloaded from 
     ftp://ftp.lineo.com/pub/busybox. 
 
 ----------------
+
 CVS:
+
 BusyBox now has its own publicly browsable CVS tree at:
     http://opensource.lineo.com/cgi-bin/cvsweb/busybox/
 
@@ -57,7 +90,6 @@ Anonymous CVS access is available.  For instructions, check out:
 For those that are actively contributing there is even CVS write access:
     http://opensource.lineo.com/cvs_write.html
 
-
 ----------------
 
 Please feed suggestions, bug reports, insults, and bribes back to:

TODO

@@ -6,36 +6,47 @@ around to it some time. If you have any good ideas, please let me know.
 * login/sulogin/passwd/getty/etc are part of tinylogin, and so are not
     needed or wanted in busybox (or else I'd have to link to libcrypt).
 
-* Networking apps are probably going to be split out some time soon into a
+* Networking apps are going to be split out to a new package called netkit-tiny
-    separate package (named perhaps netkit-tiny?).  This would remove the
+    before the next release of Busybox.  This will remove the following items
-    following items from BusyBox: hostid, hostname, nc, nslookup, telnet, and
+    from BusyBox: hostid, hostname, nc, nslookup, telnet, and ping.  nfs
-    ping.  nfs mounting and syslogd (network logging) will remain in BusyBox.
+    mounting and syslogd (network logging) will remain in BusyBox.
 
  -Erik
 
 -----------
 
-* dnsdomainname
+Possible apps to include some time:
-* traceroute/netstat
+
 * hwclock
 * stty
-* tftp
-* ftp
 * group/commonize strings, remove dups (for i18n, l10n)
 
 -----------------------
 
+The Busybox lash shell needs to be taught Bourne shell grammer.  This
+is planned for the next release of Busybox.  Look out ash, we are coming
+for you...
+
+-----------------------
+
 Running the following:
 
     rm -f busybox && make LDFLAGS+=-nostdlib 2>&1 | \
 	sed -ne 's/.*undefined reference to `\(.*\)..*/\1/gp' | sort | uniq
 
 reveals the list of all external (i.e. libc) things that BusyBox depends on.
-It would be a very nice thing to reduce this list to an absolute minimum, and
+It would be a very nice thing to reduce this list to an absolute minimum, to
-then create a microLibc to provide these functions.  There is no good reason
+reduce the footprint of busybox when staticly linking with libraries such as
-for GNU libc to be so big.  I'm sure it can be a lot better.
+uClibc.
 
-(BTW, this is more informative if BB_FEATURE_NFSMOUNT is turned off...)
+-----------------------
+
+Currently, busybox bypasses libc NSS.  Some folks might want that,
+so perhaps adding in the option to choose whether to go to libc for
+things like getpwnam() or whether to use the busybox version might 
+be nice.
+
+-----------------------
 
 Most wanted list: