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 in libcrypt).
-
-* Networking apps are probably going to be split out some time soon into a
- separate package (named perhaps tiny-netkit?). This currently includes
- hostid, hostname, mnc, and ping.
-
+* 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.
-Erik
-----------
-* Allow tar to create archives with sockets, devices, and other special files
-* Make insmod actually work
-* dnsdomainname
-* traceroute/netstat
-* rdate
-* hwclock
-* killall
-* stty
-* tr
-* cut
-* expr (maybe?) (ash builtin?)
-
-
-
------------------------
-
-
-busybox.defs.h is too big and hard to follow.
-
-I either need to add a better build system (like the Linux kernel?)
-or I need to split up busybox.defs.h into coherent chunks (i.e.
-busybox.defs.h just has a bunch of:
-
-#include "fileutils.h"
-#include "shellutils.h"
-
-which would then have smaller sets of #defines...
-Hmm. Needs to be carefully thought out.
-
------------------------
-
+Possible apps to include some time:
+* group/commonize strings, remove dups (for i18n, l10n)
-Some known bugs, todo items, etc...
-
------------------------
-
-
--rw-r--r-- 1000/1000 4398 2000-01-06 21:55 uniq.c
--rw-r--r-- 1000/1000 1568 1999-10-20 18:08 update.c
--rw-r----- 0/1000 1168 2000-01-29 21:03 update.o
--rw-r--r-- 1000/1000 22820 2000-01-05 11:36 utility.c
--rw-r----- 0/1000 7372 2000-01-29 21:03 utility.o
-tar: Skipping to next file header
-tar: Skipping to next file header
-tar: Archive - EOF not on block boundary
-tar: Error is not recoverable: exiting now
-
-
-#1 You are storing by id instead of name like normal tar. Did you realize this?
-(or am I missing some compile option? )ctar did not do this, and I don't think
-it's a good idea for LRP.
-
-#2
-ctar did not produce the EOF error like your tar does. I believe you need to
-pad the end of the archive with at least 2 tarsized (512byte) blocks. (I
-think???)
-
-#3
-There is no exclude file(s) option to tar. LRP's packaging system can not
-function without this. Will you have the time to add this soon?
+-----------
+With sysvinit, reboot, poweroff and halt all used a named pipe,
+/dev/initctl, to communicate with the init process. Busybox
+currently uses signals to communicate with init. This makes
+busybox incompatible with sysvinit. We should probably use
+a named pipe as well so we can be compatible.
-----------------------
-cd /mnt
-mkdir BACKUP
-mv * BACKUP
+Run the following:
-Today, "mv" behaved as a cp -a and my disk becomed full. It does not
-work properly either when renaming a directory into something else
-(it produces a lot of disk activity when doing this).
+ 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, to
+reduce the footprint of busybox, especially when staticly linking with
+libraries such as uClibc.
-----------------------
-
-Feature request:
-
-/bin/busybox --install -s which makes all links to commands that it
- can support (an optionnal -s should be used for symbolic links instead
- of hard links).
-
+Compile with debugging on, run 'nm --size-sort ./busybox'
+and then start with the biggest things and make them smaller...
-----------------------
+xargs could use a -l option
-> Have you ever thought of doig network logging in busybox syslogd ? It
-> would quite make sense on embedded systems... :)
-
-So far I had not considered it. Basically, you wish to have
-messages from the embedded box logged to a remote network
-syslog box, right? I can see that this would be useful.
-I'll add this to the TODO list,
+------------------------------------------------------------------
+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 .