aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--TODO36
-rw-r--r--docs/busybox.net/developer.html8
-rwxr-xr-xshell/hush_test/hush-misc/func4.tests4
3 files changed, 42 insertions, 6 deletions
diff --git a/TODO b/TODO
index 52b6bd0ba..beeb47539 100644
--- a/TODO
+++ b/TODO
@@ -282,3 +282,39 @@ Replace deprecated functions.
282--- 282---
283vdprintf() -> similar sized functionality 283vdprintf() -> similar sized functionality
284--- 284---
285
286(TODO list after discussion 11.05.2009)
287
288* shrink tc/brctl/ip
289 tc/brctl seem like fairly large things to try and tackle in your timeframe,
290 and i think people have posted attempts in the past. adding additional
291 options to ip though seems reasonable.
292
293* add tests for some applets
294
295* implement POSIX utilities and audit them for POSIX conformance. then
296 audit them for GNU conformance. then document all your findings in a new
297 doc/conformance.txt file while perhaps implementing some of the missing
298 features.
299 you can find the latest POSIX documentation (1003.1-2008) here:
300 http://www.opengroup.org/onlinepubs/9699919799/
301 and the complete list of all utilities that POSIX covers:
302 http://www.opengroup.org/onlinepubs/9699919799/idx/utilities.html
303 The first step would to generate a file/matrix what is already archived
304 (also IPV6)
305
306* ntpdate/ntpd (see ntpclient and openntp for examples)
307
308* implement 'at'
309
310* rpcbind (former portmap) or equivalent
311 so that we don't have to use -o nolock on nfs mounts
312
313* check IPV6 compliance
314
315* generate a mini example using kernel+busybox only (+libc) for example
316
317* more support for advanced linux 2.6.x features, see: iotop
318 most likely there is more
319
320* even more support for statistics: mpstat, iostat, powertop....
diff --git a/docs/busybox.net/developer.html b/docs/busybox.net/developer.html
index 18e42cd2b..ce50555ae 100644
--- a/docs/busybox.net/developer.html
+++ b/docs/busybox.net/developer.html
@@ -31,8 +31,8 @@ committing changes to GIT, and attach a public ssh key to access your account
31with.</p> 31with.</p>
32 32
33<p>If you don't currently have an ssh version 2 DSA key at least 4096 bits 33<p>If you don't currently have an ssh version 2 DSA key at least 4096 bits
34long, you can generate a key using the command 34long, you can generate a key using the command
35<b>ssh-keygen -b 4096 -t dsa</b> 35<b>ssh-keygen -b 4096 -t dsa</b>
36and hitting enter at the prompts. 36and hitting enter at the prompts.
37This will create the files <b>~/.ssh/id_dsa</b> and <b>~/.ssh/id_dsa.pub</b> 37This will create the files <b>~/.ssh/id_dsa</b> and <b>~/.ssh/id_dsa.pub</b>
38You must then send the content of 'id_dsa.pub' to me so I can set up your 38You must then send the content of 'id_dsa.pub' to me so I can set up your
@@ -75,8 +75,8 @@ git help
75<a href="http://www.kernel.org/pub/software/scm/git/">GIT</a>, please visit the 75<a href="http://www.kernel.org/pub/software/scm/git/">GIT</a>, please visit the
76<a href="http://git.or.cz/">GIT overview</a> site. 76<a href="http://git.or.cz/">GIT overview</a> site.
77You might also want to read online the <a 77You might also want to read online the <a
78href="http://www.kernel.org/pub/software/scm/git/docs">manpages</a> 78href="http://www.kernel.org/pub/software/scm/git/docs">manpages</a>
79or 79or
80<a href="http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html">tutorial</a>. 80<a href="http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html">tutorial</a>.
81</p> 81</p>
82 82
diff --git a/shell/hush_test/hush-misc/func4.tests b/shell/hush_test/hush-misc/func4.tests
index db3f15abf..33b1663f3 100755
--- a/shell/hush_test/hush-misc/func4.tests
+++ b/shell/hush_test/hush-misc/func4.tests
@@ -1,5 +1,5 @@
1func() { 1func() {
2 eval "echo \"\${val_${1}}\"" 2 eval "echo \"\${val_${1}}\""
3} 3}
4 4
5val_x=24 5val_x=24