the word "only" is repeated for CONFIG_FEATURE_SHADOWPASSWDS

[oweals/busybox.git] / TODO

diff --git a/TODO b/TODO
index 1c3b460e79b5f6bb85b949a8d1d4872d7c236b03..35bc11a24de3c17eec30d10de4812f9898424b52 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,73 +1,49 @@
 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,
 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 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.
-
-* init's waitfor() calls wait() which can catch and ignore the wrong pid 
-    exiting.  That other process is then not restarted.
-
-
+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
 
 -----------
 
 
  -Erik
 
 -----------
 

-* Allow tar to create archives with sockets, devices, and other special files
-* Make insmod actually work
-* dnsdomainname
-* traceroute/nslookup/netstat
-* rdate
-* hwclock
-* killall
-* stty
-* tr
-* expr (maybe?)  (ash builtin?)
-
+Possible apps to include some time:

 
 

+* group/commonize strings, remove dups (for i18n, l10n)

 
 

+-----------

 
 

-Some known bugs, todo items, etc...
+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.

 
 -----------------------
 
 
 -----------------------
 

+Run the following:

 
 

-[andersen@slag busybox]$ ./busybox du /bin
-6213    /bin
-[andersen@slag busybox]$ du /bin
-2971    /bin
-[andersen@slag busybox]$ du --block-size=512 /bin
-5943    /bin
+    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.

 
 

--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
+-----------------------

 
 

+Compile with debugging on, run 'nm --size-sort ./busybox'
+and then start with the biggest things and make them smaller...

 
 

-#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???)
+xargs could use a -l option

 
 

-#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?
+------------------------------------------------------------------

 
 

+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 .