Add some error messages, use xmalloc instead of malloc

[oweals/busybox.git] / README

diff --git a/README b/README
index ceda825df36b3cd9c514c19e06945dd363887b1d..14aabe66bb43a093bdc395b0ed24d3c0bc444e5d 100644 (file)
--- a/README
+++ b/README
@@ -56,36 +56,6 @@ Supported kernels:
 
 ----------------
 
-Shells:
-
-lash is the very smallest shell (adds just 10k) and it is quite usable as 
-a command prompt, but it is not suitable for any but the most trivial
-scripting (such as an initrd that calls insmod a few times) since it does
-not understand Bourne shell grammer.  It does handle pipes, redirects, and
-job control though.  Adding in command editing makes it a very nice
-lightweight command prompt.
-
-hush is also quite small (just 18k) and it has very complete Bourne shell
-grammer.  It handles if/then/else/fi just fine, but doesn't handle loops
-like for/do/done or case/esac and such.  It also currently has a problem
-with job control.  Using hush is not yet recommended.
-
-msh: The minix shell (adds just 30k) is quite complete and handles things
-like for/do/done, case/esac and all the things you expect a Bourne shell to
-do.  It is not always pedantically correct about Bourne shell grammer (try
-running the shell testscript "tests/sh.testcases" on it and compare vs bash)
-but for most things it works quite well.  It also uses only vfork, so it can
-be used on uClinux systems.  This was only recently added, so there is still
-room to shrink it further...
-
-ash: This adds about 60k in the default configuration and is the most
-complete and most pedantically correct shell included with busybox.  This
-shell was also recently added, and several people (mainly Vladimir and Erik)
-have been working on it.  There are a number of configurable things at the
-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
@@ -97,12 +67,12 @@ the mailing list if you are interested.
 Bugs:
 
 If you find bugs, please submit a detailed bug report to the busybox mailing
-list at busybox@busybox.net.  A well-written bug report should include a
+list at busybox@mail.busybox.net.  A well-written bug report should include a
 transcript of a shell session that demonstrates the bad behavior and enables
 anyone else to duplicate the bug on their own machine. The following is such 
 an example:
 
-    To: busybox@busybox.net
+    To: busybox@mail.busybox.net
     From: diligent@testing.linux.org
     Subject: /bin/date doesn't work