1999-12-03 17:19:54 +08:00
|
|
|
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.
|
1999-11-24 05:38:12 +08:00
|
|
|
|
2001-01-25 02:47:30 +08:00
|
|
|
* We _were_ going to split networking apps into a new package called
|
|
|
|
netkit-tiny. Per discussions on the mailing list, this isn't going
|
2001-01-27 17:33:39 +08:00
|
|
|
to happen. False alarm. Sorry about the confusion.
|
|
|
|
|
1999-12-03 17:19:54 +08:00
|
|
|
-Erik
|
|
|
|
|
|
|
|
-----------
|
1999-11-25 16:06:22 +08:00
|
|
|
|
2000-12-14 02:07:38 +08:00
|
|
|
Possible apps to include some time:
|
|
|
|
|
2000-05-09 07:25:59 +08:00
|
|
|
* group/commonize strings, remove dups (for i18n, l10n)
|
2000-02-07 13:29:42 +08:00
|
|
|
|
2001-02-15 02:47:33 +08:00
|
|
|
-----------
|
|
|
|
|
2001-05-04 01:35:48 +08:00
|
|
|
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.
|
2001-02-15 02:47:33 +08:00
|
|
|
|
2000-05-02 03:27:17 +08:00
|
|
|
-----------------------
|
|
|
|
|
2001-02-15 02:47:33 +08:00
|
|
|
Run the following:
|
2000-05-02 03:27:17 +08:00
|
|
|
|
2000-05-02 03:50:37 +08:00
|
|
|
rm -f busybox && make LDFLAGS+=-nostdlib 2>&1 | \
|
|
|
|
sed -ne 's/.*undefined reference to `\(.*\)..*/\1/gp' | sort | uniq
|
2000-05-02 03:27:17 +08:00
|
|
|
|
2001-05-24 04:32:09 +08:00
|
|
|
reveals the list of all external (i.e., libc) things that BusyBox depends on.
|
2000-12-14 02:07:38 +08:00
|
|
|
It would be a very nice thing to reduce this list to an absolute minimum, to
|
2001-01-25 02:47:30 +08:00
|
|
|
reduce the footprint of busybox, especially when staticly linking with
|
|
|
|
libraries such as uClibc.
|
2000-05-02 03:27:17 +08:00
|
|
|
|
2000-12-14 02:07:38 +08:00
|
|
|
-----------------------
|
|
|
|
|
2000-03-01 05:49:22 +08:00
|
|
|
Compile with debugging on, run 'nm --size-sort ./busybox'
|
|
|
|
and then start with the biggest things and make them smaller...
|
|
|
|
|
2001-04-18 01:09:34 +08:00
|
|
|
-----------------------
|
|
|
|
|
|
|
|
xargs could use a -l option
|
|
|
|
|
2000-03-23 09:09:18 +08:00
|
|
|
------------------------------------------------------------------
|
2001-12-06 11:32:12 +08:00
|
|
|
|
|
|
|
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 .
|