diff options
author | erik <erik@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2000-04-05 01:00:52 +0000 |
---|---|---|
committer | erik <erik@69ca8d6d-28ef-0310-b511-8ec308f3f277> | 2000-04-05 01:00:52 +0000 |
commit | 75841bfeb6d55a28a4fbed984de992bf4f74b4f3 (patch) | |
tree | 901159af2b1e62084f258d893949fd9b2fd2d689 /TODO | |
parent | de90251e280ca7b4fc9ec16a8b2914307feda452 (diff) | |
download | busybox-w32-75841bfeb6d55a28a4fbed984de992bf4f74b4f3.tar.gz busybox-w32-75841bfeb6d55a28a4fbed984de992bf4f74b4f3.tar.bz2 busybox-w32-75841bfeb6d55a28a4fbed984de992bf4f74b4f3.zip |
Tar now works perfectly. It behaves much better now then it
used to. Only thing left to do is add in exclude (-X) option.
-Erik
git-svn-id: svn://busybox.net/trunk/busybox@430 69ca8d6d-28ef-0310-b511-8ec308f3f277
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 53 |
1 files changed, 1 insertions, 52 deletions
@@ -15,15 +15,12 @@ around to it some time. If you have any good ideas, please let me know. | |||
15 | 15 | ||
16 | ----------- | 16 | ----------- |
17 | 17 | ||
18 | * Allow tar to create archives with sockets, devices, and other special files | ||
19 | * Make insmod actually work | 18 | * Make insmod actually work |
20 | * dnsdomainname | 19 | * dnsdomainname |
21 | * traceroute/netstat | 20 | * traceroute/netstat |
22 | * rdate | 21 | * rdate |
23 | * hwclock | 22 | * hwclock |
24 | * killall | ||
25 | * stty | 23 | * stty |
26 | * tr | ||
27 | * cut | 24 | * cut |
28 | * expr (maybe?) (ash builtin?) | 25 | * expr (maybe?) (ash builtin?) |
29 | 26 | ||
@@ -40,58 +37,17 @@ and then start with the biggest things and make them smaller... | |||
40 | 37 | ||
41 | busybox.defs.h is too big and hard to follow. | 38 | busybox.defs.h is too big and hard to follow. |
42 | 39 | ||
43 | I either need to add a better build system (like the Linux kernel?) | 40 | Perhaps I need to add a better build system (like the Linux kernel?) |
44 | or I need to split up busybox.defs.h into coherent chunks (i.e. | ||
45 | busybox.defs.h just has a bunch of: | ||
46 | |||
47 | #include "fileutils.h" | ||
48 | #include "shellutils.h" | ||
49 | |||
50 | which would then have smaller sets of #defines... | ||
51 | Hmm. Needs to be carefully thought out. | ||
52 | 41 | ||
53 | ----------------------- | 42 | ----------------------- |
54 | 43 | ||
55 | 44 | ||
56 | -rw-r--r-- 1000/1000 4398 2000-01-06 21:55 uniq.c | ||
57 | -rw-r--r-- 1000/1000 1568 1999-10-20 18:08 update.c | ||
58 | -rw-r----- 0/1000 1168 2000-01-29 21:03 update.o | ||
59 | -rw-r--r-- 1000/1000 22820 2000-01-05 11:36 utility.c | ||
60 | -rw-r----- 0/1000 7372 2000-01-29 21:03 utility.o | ||
61 | tar: Skipping to next file header | ||
62 | tar: Skipping to next file header | ||
63 | tar: Archive - EOF not on block boundary | ||
64 | tar: Error is not recoverable: exiting now | ||
65 | |||
66 | |||
67 | #1 You are storing by id instead of name like normal tar. Did you realize this? | ||
68 | (or am I missing some compile option? )ctar did not do this, and I don't think | ||
69 | it's a good idea for LRP. | ||
70 | |||
71 | #2 | ||
72 | ctar did not produce the EOF error like your tar does. I believe you need to | ||
73 | pad the end of the archive with at least 2 tarsized (512byte) blocks. (I | ||
74 | think???) | ||
75 | |||
76 | #3 | ||
77 | There is no exclude file(s) option to tar. LRP's packaging system can not | 45 | There is no exclude file(s) option to tar. LRP's packaging system can not |
78 | function without this. Will you have the time to add this soon? | 46 | function without this. Will you have the time to add this soon? |
79 | 47 | ||
80 | 48 | ||
81 | ----------------------- | 49 | ----------------------- |
82 | 50 | ||
83 | cd /mnt | ||
84 | mkdir BACKUP | ||
85 | mv * BACKUP | ||
86 | |||
87 | Today, "mv" behaved as a cp -a and my disk becomed full. It does not | ||
88 | work properly either when renaming a directory into something else | ||
89 | (it produces a lot of disk activity when doing this). | ||
90 | |||
91 | |||
92 | ----------------------- | ||
93 | |||
94 | |||
95 | Feature request: | 51 | Feature request: |
96 | 52 | ||
97 | /bin/busybox --install -s which makes all links to commands that it | 53 | /bin/busybox --install -s which makes all links to commands that it |
@@ -114,13 +70,6 @@ I'll add this to the TODO list, | |||
114 | ----------------------- | 70 | ----------------------- |
115 | 71 | ||
116 | 72 | ||
117 | In utility.c:copyFile: It uses followLinks for both source and | ||
118 | destination files... is that right for `mv'? Will need to revisit | ||
119 | the GNU, freeBSD, and MINIX versions for this... Should read the | ||
120 | Unix98 and POSIX specs also. | ||
121 | |||
122 | ----------------------- | ||
123 | |||
124 | I think that the add_inode &c in utility.c needs to also stow the | 73 | I think that the add_inode &c in utility.c needs to also stow the |
125 | st_dev field, and that du.c should NOT call `reset_inode_list' | 74 | st_dev field, and that du.c should NOT call `reset_inode_list' |
126 | because there can be hard links from inside one argv/ to inside | 75 | because there can be hard links from inside one argv/ to inside |