TODO list for busybox in no particular order. Just because something
is listed here doesn't mean that it is going to be added to busybox,
-or that doing so is even a good idea. It just means that I _might_ get
-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).
-
-* We _were_ going to split networking apps into a new package called
- netkit-tiny. Per discussions on the mailing list, this isn't going
- to happen. False alarm. Sorry about the confusion.
-
-* The default busybox shell, lash, is really too weak for serious use,
- although it is possible to run many simple systems with it. BusyBox
- 0.52 now contains a rewritten shell, hush, which understands most
- Bourne grammar, with only about a 4 Kbyte binary size penalty. You can
- engage hush at pre-compile time by "ln -sf hush.c sh.c; touch hush.c".
- Hush is young, and has plenty of bugs to shake out, so think twice before
- using it for production systems. We welcome bug reports and patches.
+or that doing so is even a good idea. It just means that we _might_ get
+around to it some time. If you have any good ideas, please send them
+on in...
-Erik
Possible apps to include some time:
-* hwclock
* group/commonize strings, remove dups (for i18n, l10n)
-----------
Compile with debugging on, run 'nm --size-sort ./busybox'
and then start with the biggest things and make them smaller...
------------------------
-
- du.c probably ought to have an -x switch like GNU du does...
-
-----------------------
xargs could use a -l option
------------------------------------------------------------------
+
+libbb/unzip.c and archival/gzip.c have common constant static arrays and
+code for initializing the CRC array. Both use CRC-32 and could use
+common code for CRC calculation. Within archival/gzip.c, the CRC
+array should be malloc-ed as it is in libbb/unzip.c .
projects / oweals / busybox.git / blobdiff