summaryrefslogtreecommitdiff
path: root/TODO
blob: 1c3b460e79b5f6bb85b949a8d1d4872d7c236b03 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
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.



 -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?)




Some known bugs, todo items, etc...

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


[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

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

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