aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRob Landley <rob@landley.net>2005-08-13 01:12:49 +0000
committerRob Landley <rob@landley.net>2005-08-13 01:12:49 +0000
commitc7cba1ae3bacb11de6a11df8c2fc98a69e423d7d (patch)
treed3fbf690db083da3d45fbe4166cc43d396dd7945
parentbe3dae145f71b583f2c975d8dcdc10d9dad2268a (diff)
downloadbusybox-w32-c7cba1ae3bacb11de6a11df8c2fc98a69e423d7d.tar.gz
busybox-w32-c7cba1ae3bacb11de6a11df8c2fc98a69e423d7d.tar.bz2
busybox-w32-c7cba1ae3bacb11de6a11df8c2fc98a69e423d7d.zip
This is published from trunk, remove from 1.0 branch.
Diffstat
-rw-r--r--busybox/docs/busybox.net/FAQ.html289
-rw-r--r--busybox/docs/busybox.net/about.html63
-rw-r--r--busybox/docs/busybox.net/busybox-growth.ps404
-rw-r--r--busybox/docs/busybox.net/copyright.txt29
-rw-r--r--busybox/docs/busybox.net/cvs_anon.html57
-rw-r--r--busybox/docs/busybox.net/cvs_howto.html44
-rw-r--r--busybox/docs/busybox.net/cvs_write.html32
-rw-r--r--busybox/docs/busybox.net/docs.html27
-rw-r--r--busybox/docs/busybox.net/download.html38
-rw-r--r--busybox/docs/busybox.net/footer.html20
-rw-r--r--busybox/docs/busybox.net/header.html81
-rw-r--r--busybox/docs/busybox.net/images/back.pngbin322 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/images/busybox.jpegbin9023 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/images/busybox.pngbin34014 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/images/busybox1.pngbin10913 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/images/busybox2.jpgbin8204 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/images/busybox3.jpgbin3292 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/images/dir.pngbin309 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/images/donate.pngbin807 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/images/fm.mini.pngbin7708 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/images/gfx_by_gimp.pngbin3955 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/images/ltbutton2.pngbin6798 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/images/sdsmall.pngbin1593 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/images/text.pngbin307 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/images/vh40.gifbin906 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/images/written.in.vi.pngbin4394 -> 0 bytes
-rw-r--r--busybox/docs/busybox.net/index.html1
-rw-r--r--busybox/docs/busybox.net/license.html135
-rw-r--r--busybox/docs/busybox.net/lists.html45
-rw-r--r--busybox/docs/busybox.net/news.html52
-rw-r--r--busybox/docs/busybox.net/oldnews.html1060
-rw-r--r--busybox/docs/busybox.net/products.html166
-rw-r--r--busybox/docs/busybox.net/screenshot.html57
-rw-r--r--busybox/docs/busybox.net/shame.html77
34 files changed, 0 insertions, 2677 deletions
diff --git a/busybox/docs/busybox.net/FAQ.html b/busybox/docs/busybox.net/FAQ.html
deleted file mode 100644
index 8de06e632..000000000
--- a/busybox/docs/busybox.net/FAQ.html
+++ /dev/null
@@ -1,289 +0,0 @@
1<!--#include file="header.html" -->
2
3
4<h3>Frequently Asked Questions</h3>
5
6This is a collection of some of the more frequently asked questions
7about BusyBox. Some of the questions even have answers. If you
8have additions to this FAQ document, we would love to add them,
9
10<ol>
11<li><a href="#kernel">Which Linux kernel versions are supported?</a>
12<li><a href="#arch">Which architectures does BusyBox run on?</a>
13<li><a href="#libc">Which C libraries are supported?</a>
14<li><a href="#commercial">Can I include BusyBox as part of the software on my device?</a>
15<li><a href="#bugs">I think I found a bug in BusyBox! What should I do?!</a>
16<li><a href="#job_control">Why do I keep getting "sh: can't access tty; job control
17 turned off" errors? Why doesn't Control-C work within my shell?</a>
18<li><a href="#demanding">I demand that you to add &lt;favorite feature&gt; right now! How come
19 you don't answer all my questions on the mailing list instantly? I demand
20 that you help me with all of my problems <em>Right Now</em>!</a>
21<li><a href="#getting_started">How can I get started using BusyBox?</a>
22<li><a href="#helpme">I need help with BusyBox! What should I do?</a>
23<li><a href="#contracts">I need you to add &lt;favorite feature&gt;! Are the BusyBox developers willing to
24 be paid in order to fix bugs or add in &lt;favorite feature&gt;? Are you willing to provide
25 support contracts?</a>
26<li><a href="#support">I think you guys are great and I want to help support your work!</a>
27
28
29</ol>
30
31
32<hr />
33<p>
34<h2><a name="kernel">Which Linux kernel versions are supported?</a></h2>
35<p>
36
37
38 Full functionality requires Linux 2.2.x or better. A large fraction of the
39 code should run on just about anything. While the current code is fairly
40 Linux specific, it should be fairly easy to port the majority of the code
41 to support, say, FreeBSD or Solaris, or Mac OS X, or even Windows (if you
42 are into that sort of thing).
43
44
45<hr />
46<p>
47<h2><a name="arch">Which architectures does BusyBox run on?</a></h2>
48<p>
49
50
51 BusyBox in general will build on any architecture supported by gcc.
52 Kernel module loading for 2.2 and 2.4 Linux kernels is currently
53 limited to ARM, CRIS, H8/300, x86, ia64, x86_64, m68k, MIPS, PowerPC,
54 S390, SH3/4/5, Sparc, v850e, and x86_64 for 2.4.x kernels.
55
56 With 2.6.x kernels, module loading support should work on all architectures.
57
58
59<hr />
60<p>
61<h2><a name="libc">Which C libraries are supported?</a></h2>
62<p>
63
64
65 uClibc and glibc are supported. People have been looking at newlib and
66 dietlibc, but they are currently considered unsupported, untested, or
67 worse. Linux-libc5 is no longer supported. If you require a small C
68 library, you should probably use uClibc.
69
70
71<hr />
72<p>
73<h2><a name="commercial">Can I include BusyBox as part of the software on my device?</h2>
74
75 Yes. As long as you <a href="http://busybox.net/license.html">fully comply
76 with the generous terms of the GPL BusyBox license</a> you can ship BusyBox
77 as part of the software on your device.
78
79 <a href="#support">Please consider sharing some of the money you make.</a>
80
81
82<hr />
83<p>
84<h2><a name="bugs">I think I found a bug in BusyBox! What should I do?</h2>
85<p>
86
87 If you find a problem with BusyBox, please submit a detailed bug report to
88 the BusyBox mailing list at <a href="mailto:busybox@mail.busybox.net">
89 busybox@mail.busybox.net</a>. Please do not send private email to Erik
90 (the maintainer of BusyBox) asking for private help unless you are planning
91 on paying for consulting services. When we answer questions on the BusyBox
92 mailing list, it helps everyone, while private answers help only you...
93
94 <p>
95
96 If you find bugs, please submit a detailed bug report to the BusyBox mailing
97 list at busybox@mail.busybox.net. A well-written bug report should include a
98 transcript of a shell session that demonstrates the bad behavior and enables
99 anyone else to duplicate the bug on their own machine. The following is such
100 an example:
101
102<pre>
103 To: busybox@mail.busybox.net
104 From: diligent@testing.linux.org
105 Subject: /bin/date doesn't work
106
107 Package: BusyBox
108 Version: 1.00
109
110 When I execute BusyBox 'date' it produces unexpected results.
111 With GNU date I get the following output:
112
113 $ date
114 Fri Oct 8 14:19:41 MDT 2004
115
116 But when I use BusyBox date I get this instead:
117
118 $ date
119 illegal instruction
120
121 I am using Debian unstable, kernel version 2.4.27 on a x86 system,
122 and the latest uClibc from CVS. Thanks for the wonderful program!
123
124 -Diligent
125</pre>
126
127 Note the careful description and use of examples showing not only what BusyBox
128 does, but also a counter example showing what an equivalent GNU app does. Bug
129 reports lacking proper detail may never be fixed... Thanks for understanding.
130
131<hr />
132<p>
133<h2><a name="job_control">Why do I keep getting "sh: can't access tty; job control
134 turned off" errors? Why doesn't Control-C work within my shell?</a></h2>
135<p>
136
137 Job control will be turned off since your shell can not obtain a controlling
138 terminal. This typically happens when you run your shell on /dev/console.
139 The kernel will not provide a controlling terminal on the /dev/console
140 device. Your should run your shell on a normal tty such as tty1 or ttyS0
141 and everything will work perfectly. If you <em>REALLY</em> want your shell
142 to run on /dev/console, then you can hack your kernel (if you are into that
143 sortof thing) by changing drivers/char/tty_io.c to change the lines where
144 it sets "noctty = 1;" to instead set it to "0". I recommend you instead
145 run your shell on a real console...
146
147
148<hr />
149<p>
150<h2><a name="getting_started">How can I get started using BusyBox?</a></h2>
151<p>
152
153 An easy method to build your own basic BusyBox based system, is to
154 follow these simple steps:
155 <ul>
156 <li> Point your web browser <a href="/cgi-bin/cvsweb/buildroot/">here</a>
157 <li> Click on "Download tarball"
158 <li> Unpack the tarball on your Linux system somewhere
159 <li> run 'make' and configure things to taste.
160 <li> run 'unset CC'. Some Linux systems (i.e. Gentoo) set 'CC'
161 in the system environment which messes up cross compiles.
162 <li> run 'make'
163 <li> go have lunch, drink a pop, call a friend, play a video game, etc
164 till it finishes downloading software and compiling things.
165 <li> You should now have a shiny new BusyBox based system.
166 </ul>
167
168
169<hr />
170<p>
171<h2><a name="demanding">I demand that you to add &lt;favorite feature&gt; right now! How come
172 you don't answer all my questions on the mailing list instantly? I demand
173 that you help me with all of my problems <em>Right Now</em>!</a></h2>
174<p>
175
176 You have not paid us a single cent and yet you still have the product of
177 many years of our work. We are not your slaves! We work on BusyBox
178 because we find it useful and interesting. If you go off flaming us, we
179 will ignore you.
180
181
182<hr />
183<p>
184<h2><a name="helpme">I need help with BusyBox! What should I do?</a></h2>
185<p>
186
187 If you find that you need help with BusyBox, you can ask for help on the
188 BusyBox mailing list at busybox@mail.busybox.net. In addition to the BusyBox
189 mailing list, Erik (andersee), Manuel (mjn3) and others are known to hang out
190 on the uClibc IRC channel: #uclibc on irc.freenode.net.
191
192 <p>
193
194 <b>Please do not send private email to Erik, Manuel, or the other BusyBox
195 contributors asking for private help unless you are planning on paying for
196 consulting services.</b>
197
198 <p>
199
200 When we answer questions on the BusyBox mailing list, it helps everyone
201 since people with similar problems in the future will be able to get help
202 by searching the mailing list archives. Private help is reserved as a paid
203 service. If you need to use private communication, or if you are serious
204 about getting timely assistance with BusyBox, you should seriously consider
205 paying for consulting services.
206
207 <p>
208
209
210
211<hr />
212<p>
213<h2><a name="contracts">I need you to add &lt;favorite feature&gt;! Are the BusyBox
214 developers willing to be paid in order to fix bugs or add in &lt;favorite feature&gt;?
215 Are you willing to provide support contracts?</a></h2>
216<p>
217
218 Sure! Now you have our attention! What you should do is contact <a
219 href="mailto:andersen@codepoet.org">Erik Andersen</a> of <a
220 href="http://codepoet-consulting.com/">CodePoet Consulting</a> to bid
221 on your project. If Erik is too busy to personally add your feature, there
222 are many other active BusyBox contributors who will almost certainly be able
223 to help you out. Erik can contact them privatly, and may even let you to
224 post your request for services on the mailing list.
225
226
227<hr />
228<p>
229<h2><a name="support">I think you guys are great and I want to help support your work!</a></h2>
230<p>
231
232 Wow, that would be great! Erik personally pays for all the bandwidth, and
233 all servers used for busybox.net out of his own pocket. If you would like
234 to make a donation to help support BusyBox, and/or request features, you
235 can click here:
236
237 <!-- Begin PayPal Logo -->
238 <center>
239 <form action="https://www.paypal.com/cgi-bin/webscr" method="post">
240 <input type="hidden" name="cmd" value="_xclick">
241 <input type="hidden" name="business" value="andersen@codepoet.org">
242 <input type="hidden" name="item_name" value="Support BusyBox">
243 <input type="hidden" name="image_url" value="http://codepoet-consulting.com/images/codepoet.png">
244 <input type="hidden" name="no_shipping" value="1">
245 <input type="image" src="images/donate.png" name="submit" alt="Make donation using PayPal">
246 </form>
247 </center>
248 <!-- End PayPal Logo -->
249
250 If you prefer to contact Erik directly to make a donation, donate hardware,
251 request support, etc, you can contact
252 <a href="http://codepoet-consulting.com/">CodePoet Consulting</a> here.
253 CodePoet Consulting can accept both Visa and MasterCard for those that do not
254 trust PayPal...
255
256<hr />
257<p>
258<h2><a name="optimize">I want to make busybox even smaller, how do I go about it?</a></h2>
259<p>
260 To conserve bytes it's good to know where they're being used, and the
261 size of the final executable isn't always a reliable indicator of
262 the size of the components (since various structures are rounded up,
263 so a small change may not even be visible by itself, but many small
264 savings add up).
265</p>
266<p>
267 To examine a busybox binary with an eye to saving bytes, build an
268 optimized debug version and run the "nm" command against it, like so:
269</p>
270<p>
271 make clean && make STRIPCMD=/bin/true && nm --size-sort busybox
272</p>
273<p>
274 This gives a list of symbols and the amount of space allocated for
275 each one, sorted by size. (Note: do not enable CONFIG_DEBUG for this,
276 as that disables compiler optimization which is great for running gdb
277 but misleading when trying to figure out how much space each component
278 is really using under normal circumstances.)
279</p>
280<hr />
281
282
283
284<br>
285<br>
286<br>
287
288<!--#include file="footer.html" -->
289
diff --git a/busybox/docs/busybox.net/about.html b/busybox/docs/busybox.net/about.html
deleted file mode 100644
index c08626386..000000000
--- a/busybox/docs/busybox.net/about.html
+++ /dev/null
@@ -1,63 +0,0 @@
1<!--#include file="header.html" -->
2
3
4<!-- Begin Introduction section -->
5
6<h3>BusyBox: The Swiss Army Knife of Embedded Linux</h3>
7
8
9BusyBox combines tiny versions of many common UNIX utilities into a single
10small executable. It provides replacements for most of the utilities you
11usually find in GNU fileutils, shellutils, etc. The utilities in BusyBox
12generally have fewer options than their full-featured GNU cousins; however,
13the options that are included provide the expected functionality and behave
14very much like their GNU counterparts. BusyBox provides a fairly complete
15environment for any small or embedded system.
16
17<p>
18
19BusyBox has been written with size-optimization and limited resources in
20mind. It is also extremely modular so you can easily include or exclude
21commands (or features) at compile time. This makes it easy to customize
22your embedded systems. To create a working system, just add some device
23nodes in /dev, a few configuration files in /etc, and a Linux kernel.
24
25<p>
26
27BusyBox is maintained by <a href=
28"http://codepoet.org/andersen/erik/erik.html">Erik Andersen</a>, and
29licensed under the
30<a href= "http://www.gnu.org/copyleft/gpl.html">GNU GENERAL PUBLIC LICENSE</a>
31
32<p>
33<p>
34
35<h3>Sponsors</h3>
36
37Please visit our sponsors and thank them for their
38support! They have provided money for equipment and
39bandwidth. Next time you need help with a project,
40consider these fine companies!
41
42
43<ul>
44 <li><a href="http://www.penguru.net">Penguru Consulting</a><br>
45 Custom development for embedded Linux systems and multimedia platforms
46 </li>
47
48 <li><a href="http://opensource.se/">opensource.se</a><br>
49 Embedded open source consulting in Europe.
50 </li>
51
52 <li><a href="http://www.codepoet-consulting.com">Codepoet Consulting</a><br>
53 Custom Linux, embedded Linux, BusyBox, and uClibc
54 development.
55 </li>
56
57</ul>
58
59If you wish to be a sponsor, or if you have already contributed and would like
60your name added here, email <a href= "mailto:andersen@codepoet.org">Erik</a>.
61
62
63<!--#include file="footer.html" -->
diff --git a/busybox/docs/busybox.net/busybox-growth.ps b/busybox/docs/busybox.net/busybox-growth.ps
deleted file mode 100644
index 2379defa4..000000000
--- a/busybox/docs/busybox.net/busybox-growth.ps
+++ /dev/null
@@ -1,404 +0,0 @@
1%!PS-Adobe-2.0
2%%Title: busybox-growth.ps
3%%Creator: gnuplot 3.5 (pre 3.6) patchlevel beta 347
4%%CreationDate: Tue Apr 10 14:03:36 2001
5%%DocumentFonts: (atend)
6%%BoundingBox: 50 40 554 770
7%%Orientation: Landscape
8%%Pages: (atend)
9%%EndComments
10/gnudict 120 dict def
11gnudict begin
12/Color true def
13/Solid true def
14/gnulinewidth 5.000 def
15/userlinewidth gnulinewidth def
16/vshift -46 def
17/dl {10 mul} def
18/hpt_ 31.5 def
19/vpt_ 31.5 def
20/hpt hpt_ def
21/vpt vpt_ def
22/M {moveto} bind def
23/L {lineto} bind def
24/R {rmoveto} bind def
25/V {rlineto} bind def
26/vpt2 vpt 2 mul def
27/hpt2 hpt 2 mul def
28/Lshow { currentpoint stroke M
29 0 vshift R show } def
30/Rshow { currentpoint stroke M
31 dup stringwidth pop neg vshift R show } def
32/Cshow { currentpoint stroke M
33 dup stringwidth pop -2 div vshift R show } def
34/UP { dup vpt_ mul /vpt exch def hpt_ mul /hpt exch def
35 /hpt2 hpt 2 mul def /vpt2 vpt 2 mul def } def
36/DL { Color {setrgbcolor Solid {pop []} if 0 setdash }
37 {pop pop pop Solid {pop []} if 0 setdash} ifelse } def
38/BL { stroke gnulinewidth 2 mul setlinewidth } def
39/AL { stroke gnulinewidth 2 div setlinewidth } def
40/UL { gnulinewidth mul /userlinewidth exch def } def
41/PL { stroke userlinewidth setlinewidth } def
42/LTb { BL [] 0 0 0 DL } def
43/LTa { AL [1 dl 2 dl] 0 setdash 0 0 0 setrgbcolor } def
44/LT0 { PL [] 1 0 0 DL } def
45/LT1 { PL [4 dl 2 dl] 0 1 0 DL } def
46/LT2 { PL [2 dl 3 dl] 0 0 1 DL } def
47/LT3 { PL [1 dl 1.5 dl] 1 0 1 DL } def
48/LT4 { PL [5 dl 2 dl 1 dl 2 dl] 0 1 1 DL } def
49/LT5 { PL [4 dl 3 dl 1 dl 3 dl] 1 1 0 DL } def
50/LT6 { PL [2 dl 2 dl 2 dl 4 dl] 0 0 0 DL } def
51/LT7 { PL [2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 1 0.3 0 DL } def
52/LT8 { PL [2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 2 dl 4 dl] 0.5 0.5 0.5 DL } def
53/Pnt { stroke [] 0 setdash
54 gsave 1 setlinecap M 0 0 V stroke grestore } def
55/Dia { stroke [] 0 setdash 2 copy vpt add M
56 hpt neg vpt neg V hpt vpt neg V
57 hpt vpt V hpt neg vpt V closepath stroke
58 Pnt } def
59/Pls { stroke [] 0 setdash vpt sub M 0 vpt2 V
60 currentpoint stroke M
61 hpt neg vpt neg R hpt2 0 V stroke
62 } def
63/Box { stroke [] 0 setdash 2 copy exch hpt sub exch vpt add M
64 0 vpt2 neg V hpt2 0 V 0 vpt2 V
65 hpt2 neg 0 V closepath stroke
66 Pnt } def
67/Crs { stroke [] 0 setdash exch hpt sub exch vpt add M
68 hpt2 vpt2 neg V currentpoint stroke M
69 hpt2 neg 0 R hpt2 vpt2 V stroke } def
70/TriU { stroke [] 0 setdash 2 copy vpt 1.12 mul add M
71 hpt neg vpt -1.62 mul V
72 hpt 2 mul 0 V
73 hpt neg vpt 1.62 mul V closepath stroke
74 Pnt } def
75/Star { 2 copy Pls Crs } def
76/BoxF { stroke [] 0 setdash exch hpt sub exch vpt add M
77 0 vpt2 neg V hpt2 0 V 0 vpt2 V
78 hpt2 neg 0 V closepath fill } def
79/TriUF { stroke [] 0 setdash vpt 1.12 mul add M
80 hpt neg vpt -1.62 mul V
81 hpt 2 mul 0 V
82 hpt neg vpt 1.62 mul V closepath fill } def
83/TriD { stroke [] 0 setdash 2 copy vpt 1.12 mul sub M
84 hpt neg vpt 1.62 mul V
85 hpt 2 mul 0 V
86 hpt neg vpt -1.62 mul V closepath stroke
87 Pnt } def
88/TriDF { stroke [] 0 setdash vpt 1.12 mul sub M
89 hpt neg vpt 1.62 mul V
90 hpt 2 mul 0 V
91 hpt neg vpt -1.62 mul V closepath fill} def
92/DiaF { stroke [] 0 setdash vpt add M
93 hpt neg vpt neg V hpt vpt neg V
94 hpt vpt V hpt neg vpt V closepath fill } def
95/Pent { stroke [] 0 setdash 2 copy gsave
96 translate 0 hpt M 4 {72 rotate 0 hpt L} repeat
97 closepath stroke grestore Pnt } def
98/PentF { stroke [] 0 setdash gsave
99 translate 0 hpt M 4 {72 rotate 0 hpt L} repeat
100 closepath fill grestore } def
101/Circle { stroke [] 0 setdash 2 copy
102 hpt 0 360 arc stroke Pnt } def
103/CircleF { stroke [] 0 setdash hpt 0 360 arc fill } def
104/C0 { BL [] 0 setdash 2 copy moveto vpt 90 450 arc } bind def
105/C1 { BL [] 0 setdash 2 copy moveto
106 2 copy vpt 0 90 arc closepath fill
107 vpt 0 360 arc closepath } bind def
108/C2 { BL [] 0 setdash 2 copy moveto
109 2 copy vpt 90 180 arc closepath fill
110 vpt 0 360 arc closepath } bind def
111/C3 { BL [] 0 setdash 2 copy moveto
112 2 copy vpt 0 180 arc closepath fill
113 vpt 0 360 arc closepath } bind def
114/C4 { BL [] 0 setdash 2 copy moveto
115 2 copy vpt 180 270 arc closepath fill
116 vpt 0 360 arc closepath } bind def
117/C5 { BL [] 0 setdash 2 copy moveto
118 2 copy vpt 0 90 arc
119 2 copy moveto
120 2 copy vpt 180 270 arc closepath fill
121 vpt 0 360 arc } bind def
122/C6 { BL [] 0 setdash 2 copy moveto
123 2 copy vpt 90 270 arc closepath fill
124 vpt 0 360 arc closepath } bind def
125/C7 { BL [] 0 setdash 2 copy moveto
126 2 copy vpt 0 270 arc closepath fill
127 vpt 0 360 arc closepath } bind def
128/C8 { BL [] 0 setdash 2 copy moveto
129 2 copy vpt 270 360 arc closepath fill
130 vpt 0 360 arc closepath } bind def
131/C9 { BL [] 0 setdash 2 copy moveto
132 2 copy vpt 270 450 arc closepath fill
133 vpt 0 360 arc closepath } bind def
134/C10 { BL [] 0 setdash 2 copy 2 copy moveto vpt 270 360 arc closepath fill
135 2 copy moveto
136 2 copy vpt 90 180 arc closepath fill
137 vpt 0 360 arc closepath } bind def
138/C11 { BL [] 0 setdash 2 copy moveto
139 2 copy vpt 0 180 arc closepath fill
140 2 copy moveto
141 2 copy vpt 270 360 arc closepath fill
142 vpt 0 360 arc closepath } bind def
143/C12 { BL [] 0 setdash 2 copy moveto
144 2 copy vpt 180 360 arc closepath fill
145 vpt 0 360 arc closepath } bind def
146/C13 { BL [] 0 setdash 2 copy moveto
147 2 copy vpt 0 90 arc closepath fill
148 2 copy moveto
149 2 copy vpt 180 360 arc closepath fill
150 vpt 0 360 arc closepath } bind def
151/C14 { BL [] 0 setdash 2 copy moveto
152 2 copy vpt 90 360 arc closepath fill
153 vpt 0 360 arc } bind def
154/C15 { BL [] 0 setdash 2 copy vpt 0 360 arc closepath fill
155 vpt 0 360 arc closepath } bind def
156/Rec { newpath 4 2 roll moveto 1 index 0 rlineto 0 exch rlineto
157 neg 0 rlineto closepath } bind def
158/Square { dup Rec } bind def
159/Bsquare { vpt sub exch vpt sub exch vpt2 Square } bind def
160/S0 { BL [] 0 setdash 2 copy moveto 0 vpt rlineto BL Bsquare } bind def
161/S1 { BL [] 0 setdash 2 copy vpt Square fill Bsquare } bind def
162/S2 { BL [] 0 setdash 2 copy exch vpt sub exch vpt Square fill Bsquare } bind def
163/S3 { BL [] 0 setdash 2 copy exch vpt sub exch vpt2 vpt Rec fill Bsquare } bind def
164/S4 { BL [] 0 setdash 2 copy exch vpt sub exch vpt sub vpt Square fill Bsquare } bind def
165/S5 { BL [] 0 setdash 2 copy 2 copy vpt Square fill
166 exch vpt sub exch vpt sub vpt Square fill Bsquare } bind def
167/S6 { BL [] 0 setdash 2 copy exch vpt sub exch vpt sub vpt vpt2 Rec fill Bsquare } bind def
168/S7 { BL [] 0 setdash 2 copy exch vpt sub exch vpt sub vpt vpt2 Rec fill
169 2 copy vpt Square fill
170 Bsquare } bind def
171/S8 { BL [] 0 setdash 2 copy vpt sub vpt Square fill Bsquare } bind def
172/S9 { BL [] 0 setdash 2 copy vpt sub vpt vpt2 Rec fill Bsquare } bind def
173/S10 { BL [] 0 setdash 2 copy vpt sub vpt Square fill 2 copy exch vpt sub exch vpt Square fill
174 Bsquare } bind def
175/S11 { BL [] 0 setdash 2 copy vpt sub vpt Square fill 2 copy exch vpt sub exch vpt2 vpt Rec fill
176 Bsquare } bind def
177/S12 { BL [] 0 setdash 2 copy exch vpt sub exch vpt sub vpt2 vpt Rec fill Bsquare } bind def
178/S13 { BL [] 0 setdash 2 copy exch vpt sub exch vpt sub vpt2 vpt Rec fill
179 2 copy vpt Square fill Bsquare } bind def
180/S14 { BL [] 0 setdash 2 copy exch vpt sub exch vpt sub vpt2 vpt Rec fill
181 2 copy exch vpt sub exch vpt Square fill Bsquare } bind def
182/S15 { BL [] 0 setdash 2 copy Bsquare fill Bsquare } bind def
183/D0 { gsave translate 45 rotate 0 0 S0 stroke grestore } bind def
184/D1 { gsave translate 45 rotate 0 0 S1 stroke grestore } bind def
185/D2 { gsave translate 45 rotate 0 0 S2 stroke grestore } bind def
186/D3 { gsave translate 45 rotate 0 0 S3 stroke grestore } bind def
187/D4 { gsave translate 45 rotate 0 0 S4 stroke grestore } bind def
188/D5 { gsave translate 45 rotate 0 0 S5 stroke grestore } bind def
189/D6 { gsave translate 45 rotate 0 0 S6 stroke grestore } bind def
190/D7 { gsave translate 45 rotate 0 0 S7 stroke grestore } bind def
191/D8 { gsave translate 45 rotate 0 0 S8 stroke grestore } bind def
192/D9 { gsave translate 45 rotate 0 0 S9 stroke grestore } bind def
193/D10 { gsave translate 45 rotate 0 0 S10 stroke grestore } bind def
194/D11 { gsave translate 45 rotate 0 0 S11 stroke grestore } bind def
195/D12 { gsave translate 45 rotate 0 0 S12 stroke grestore } bind def
196/D13 { gsave translate 45 rotate 0 0 S13 stroke grestore } bind def
197/D14 { gsave translate 45 rotate 0 0 S14 stroke grestore } bind def
198/D15 { gsave translate 45 rotate 0 0 S15 stroke grestore } bind def
199/DiaE { stroke [] 0 setdash vpt add M
200 hpt neg vpt neg V hpt vpt neg V
201 hpt vpt V hpt neg vpt V closepath stroke } def
202/BoxE { stroke [] 0 setdash exch hpt sub exch vpt add M
203 0 vpt2 neg V hpt2 0 V 0 vpt2 V
204 hpt2 neg 0 V closepath stroke } def
205/TriUE { stroke [] 0 setdash vpt 1.12 mul add M
206 hpt neg vpt -1.62 mul V
207 hpt 2 mul 0 V
208 hpt neg vpt 1.62 mul V closepath stroke } def
209/TriDE { stroke [] 0 setdash vpt 1.12 mul sub M
210 hpt neg vpt 1.62 mul V
211 hpt 2 mul 0 V
212 hpt neg vpt -1.62 mul V closepath stroke } def
213/PentE { stroke [] 0 setdash gsave
214 translate 0 hpt M 4 {72 rotate 0 hpt L} repeat
215 closepath stroke grestore } def
216/CircE { stroke [] 0 setdash
217 hpt 0 360 arc stroke } def
218/Opaque { gsave closepath 1 setgray fill grestore 0 setgray closepath } def
219/DiaW { stroke [] 0 setdash vpt add M
220 hpt neg vpt neg V hpt vpt neg V
221 hpt vpt V hpt neg vpt V Opaque stroke } def
222/BoxW { stroke [] 0 setdash exch hpt sub exch vpt add M
223 0 vpt2 neg V hpt2 0 V 0 vpt2 V
224 hpt2 neg 0 V Opaque stroke } def
225/TriUW { stroke [] 0 setdash vpt 1.12 mul add M
226 hpt neg vpt -1.62 mul V
227 hpt 2 mul 0 V
228 hpt neg vpt 1.62 mul V Opaque stroke } def
229/TriDW { stroke [] 0 setdash vpt 1.12 mul sub M
230 hpt neg vpt 1.62 mul V
231 hpt 2 mul 0 V
232 hpt neg vpt -1.62 mul V Opaque stroke } def
233/PentW { stroke [] 0 setdash gsave
234 translate 0 hpt M 4 {72 rotate 0 hpt L} repeat
235 Opaque stroke grestore } def
236/CircW { stroke [] 0 setdash
237 hpt 0 360 arc Opaque stroke } def
238/BoxFill { gsave Rec 1 setgray fill grestore } def
239end
240%%EndProlog
241%%Page: 1 1
242gnudict begin
243gsave
24450 50 translate
2450.100 0.100 scale
24690 rotate
2470 -5040 translate
2480 setgray
249newpath
250(Helvetica) findfont 140 scalefont setfont
2511.000 UL
252LTb
253560 420 M
25463 0 V
2556409 0 R
256-63 0 V
257476 420 M
258(0) Rshow
259560 1056 M
26063 0 V
2616409 0 R
262-63 0 V
263-6493 0 R
264(100) Rshow
265560 1692 M
26663 0 V
2676409 0 R
268-63 0 V
269-6493 0 R
270(200) Rshow
271560 2328 M
27263 0 V
2736409 0 R
274-63 0 V
275-6493 0 R
276(300) Rshow
277560 2964 M
27863 0 V
2796409 0 R
280-63 0 V
281-6493 0 R
282(400) Rshow
283560 3600 M
28463 0 V
2856409 0 R
286-63 0 V
287-6493 0 R
288(500) Rshow
289560 4236 M
29063 0 V
2916409 0 R
292-63 0 V
293-6493 0 R
294(600) Rshow
295560 4872 M
29663 0 V
2976409 0 R
298-63 0 V
299-6493 0 R
300(700) Rshow
3011531 420 M
3020 63 V
3030 4389 R
3040 -63 V
3050 -4529 R
306(400) Cshow
3072825 420 M
3080 63 V
3090 4389 R
3100 -63 V
3110 -4529 R
312(600) Cshow
3134120 420 M
3140 63 V
3150 4389 R
3160 -63 V
3170 -4529 R
318(800) Cshow
3195414 420 M
3200 63 V
3210 4389 R
3220 -63 V
3230 -4529 R
324(1000) Cshow
3256708 420 M
3260 63 V
3270 4389 R
3280 -63 V
3290 -4529 R
330(1200) Cshow
3311.000 UL
332LTb
333560 420 M
3346472 0 V
3350 4452 V
336-6472 0 V
337560 420 L
3380 2646 M
339currentpoint gsave translate 90 rotate 0 0 M
340(tar.gz size \(Kb\)) Cshow
341grestore
3423796 140 M
343(time \(days since Jan 1, 1998\)) Cshow
3441.000 UL
345LT0
346696 420 M
3470 593 V
3481255 0 V
3490 15 V
350214 0 V
3510 6 V
352958 0 V
3530 1 V
354-84 0 V
3550 37 V
356168 0 V
3570 262 V
35813 0 V
3590 56 V
36091 0 V
3610 33 V
3626 0 V
3630 1 V
36419 0 V
3650 11 V
36620 0 V
3670 13 V
36832 0 V
3690 104 V
37052 0 V
3710 27 V
37265 0 V
3730 15 V
37439 0 V
3750 126 V
376174 0 V
3770 103 V
37852 0 V
3790 49 V
380175 0 V
3810 56 V
382433 0 V
3830 661 V
384415 0 V
3850 857 V
386123 0 V
3870 -291 V
388498 0 V
3890 208 V
390505 0 V
3910 66 V
392291 0 V
3930 115 V
394311 0 V
3950 449 V
396162 0 V
3970 309 V
398stroke
399grestore
400end
401showpage
402%%Trailer
403%%DocumentFonts: Helvetica
404%%Pages: 1
diff --git a/busybox/docs/busybox.net/copyright.txt b/busybox/docs/busybox.net/copyright.txt
deleted file mode 100644
index 528338da9..000000000
--- a/busybox/docs/busybox.net/copyright.txt
+++ /dev/null
@@ -1,29 +0,0 @@
1
2The code and graphics on this website (and it's mirror sites, if any) are
3Copyright (c) 1999-2004 by Erik Andersen. All rights reserved.
4
5Documents on this Web site including their graphical elements, design, and
6layout are protected by trade dress and other laws and MAY BE COPIED OR
7IMITATED IN WHOLE OR IN PART. THIS WEBSITE IS LICENSED FREE OF CHARGE, THERE
8IS NO WARRANTY FOR THE WEBSITE TO THE EXTENT PERMITTED BY APPLICABLE LAW.
9SHOULD THIS WEBSITE PROVE DEFECTIVE, YOU MAY ASSUME THAT SOMEONE MIGHT GET
10AROUND TO SERVICING, REPAIRING OR CORRECTING IT SOMETIME WHEN THEY HAVE NOTHING
11BETTER TO DO. REGARDLESS, YOU GET TO KEEP BOTH PIECES.
12
13IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY
14COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THIS
15WEBSITE AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
16GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR
17INABILITY TO USE THIS WEBSITE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR
18LOSS OF HAIR, LOSS OF LIFE, LOSS OF MEMORY, LOSS OF YOUR CARKEYS, MISPLACEMENT
19OF YOUR PAYCHECK, OR COMMANDER DATA BEING RENDERED UNABLE TO ASSIST THE
20STARFLEET OFFICERS ABORD THE STARSHIP ENTERPRISE TO RECALIBRATE THE MAIN
21DEFLECTOR ARRAY, LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE
22WEBSITE TO OPERATE WITH YOUR WEBBROWSER), EVEN IF SUCH HOLDER OR OTHER PARTY
23HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
24
25You have been warned.
26
27You can contact the webmaster at <andersen@codepoet.org> if you have some sort
28of problem with this.
29
diff --git a/busybox/docs/busybox.net/cvs_anon.html b/busybox/docs/busybox.net/cvs_anon.html
deleted file mode 100644
index f823d0535..000000000
--- a/busybox/docs/busybox.net/cvs_anon.html
+++ /dev/null
@@ -1,57 +0,0 @@
1<!--#include file="header.html" -->
2
3
4<h3>Anonymous CVS</h3>
5
6We allow anonymous (read-only) CVS access to everyone. The first command you
7need to run for anonymous CVS access is:
8<pre>
9cvs -d:pserver:anonymous@busybox.net:/var/cvs login</pre>
10<p>
11CVS will prompt you for a password. Just press the Enter key (there is no
12password for anonymous access). This step only needs to be done once, the first
13time you attempt to access CVS.
14<p>
15Once the login is complete, you can then check the list of available
16CVS modules by running the following command (all on one line):
17<pre>
18cvs -z3 -d:pserver:anonymous@busybox.net:/var/cvs co -c </pre>
19
20<p>
21If you wish, you can then check out a local copy of any of the
22available modules. The following is an example of how to grab
23a copy of busybox and tinylogin:
24<pre>
25 cvs -z3 -d:pserver:anonymous@busybox.net:/var/cvs co -P busybox tinylogin</pre>
26This will create a directory called <b>busybox</b> and a directory called
27<b>tinylogin</b> in the current directory. These directories contain the
28latest and greatest source code for busybox and tinylogin.
29
30<p>
31If you are not already familiar with using CVS, I recommend you visit
32this quick <a href="/cvs_howto.html">Introduction to CVS</a>.
33
34<p>
35I usually create a ~/.cvsrc file with the following things in it, and I
36recommend you should use the same:
37<pre>
38 -z3
39 update -dP
40 rdiff -u
41 diff -ubBwpN
42 checkout -P</pre>
43
44<p>
45Once you've checked out a copy of the source tree, you can update your
46source tree at any time so it is in sync with the latest and greatest by
47running the command:
48<pre>
49cvs update</pre>
50
51Because you've only been granted anonymous access to the tree, you won't be
52able to commit any changes. Changes can be submitted for inclusion by posting
53them to the appropriate mailing list. For those that are actively contributing
54<a href="cvs_write.html">CVS write access</a> can be made available.
55
56<!--#include file="footer.html" -->
57
diff --git a/busybox/docs/busybox.net/cvs_howto.html b/busybox/docs/busybox.net/cvs_howto.html
deleted file mode 100644
index 837d6cd61..000000000
--- a/busybox/docs/busybox.net/cvs_howto.html
+++ /dev/null
@@ -1,44 +0,0 @@
1<!--#include file="header.html" -->
2
3
4<h3>How to use CVS</h3>
5
6
7If you want to know all the gory details, you will want to visit
8<a href="http://www.cvshome.org/">the CVS main web page</a>.<p>
9For the impatient, the following is probably about all you need to know:
10<p>
11
12<dl>
13 <dt><pre>cvs checkout -c</pre>
14 <dd>Will list the modules available for checkout
15 <dt><pre>cvs checkout &lt module name &gt</pre>
16 <dd>Will checkout the named module
17 <dt><pre>cvs co &lt module name &gt</pre>
18 <dd>Same thing
19 <dt><pre>cvs update</pre>
20
21 <dd>Updates your local archive so it is in sync with the repository
22 -- your local updates are left intact. Tries to merge upstream updates
23 into your local updates. You will see the following tags when it is
24 updating your local repository: C means conflict, U means update,
25 P means patched, and M means modified.
26 <dt><pre>cvs up</pre>
27 <dd>Same thing
28 <dt><pre>cvs update &lt file name &gt</pre>
29 <dd>Same thing but for just the named file(s)/directory(s).
30 <dt><pre>cvs commit</pre>
31 <dd>Will check in all your work.
32 <dt><pre>cvs add &lt file name &gt</pre>
33
34 <dd>Adds the named file/directory into CVS
35 <dt><pre>cvs remove &lt file name &gt</pre>
36 <dd>Removes the named file/directory from the upstream repository.
37 <dt><pre>cvs rm &lt file name &gt</pre>
38 <dd>Same thing
39 <dt><pre>cvs log &lt file name &gt</pre>
40</dl>
41
42
43<!--#include file="footer.html" -->
44
diff --git a/busybox/docs/busybox.net/cvs_write.html b/busybox/docs/busybox.net/cvs_write.html
deleted file mode 100644
index 5c882f48f..000000000
--- a/busybox/docs/busybox.net/cvs_write.html
+++ /dev/null
@@ -1,32 +0,0 @@
1<!--#include file="header.html" -->
2
3
4<h3>CVS Read/Write Access</h3>
5
6If you want to be able to commit things to CVS, first contribute some
7stuff to show you are serious. Then, very nicely ask
8<a href="mailto:andersen@codepoet.org">Erik Andersen</a> if he will set you up with
9an account. To access CVS, you will want to add the following to set up your environment:
10<pre>
11$ export CVS_RSH=/usr/bin/ssh
12$ export CVSROOT='username@cvs.busybox.net:/var/cvs'</pre>
13<br>
14It goes without saying you must change <em>username</em> to your own
15username...
16<p>
17
18To obtain commit access, you will need to demonstrate you are
19serious by submitting a few good patches first. Then, you will need to
20select a user-name to use when committing stuff, and finally, you will
21need to send me the username you have selected, an ssh key, and the email
22address where you prefer email to be sent (I will forward any email sent
23to you, but not store it).
24
25<p>
26Note that if you would prefer to keep your communications with me
27private, you can encrypt your email using my
28<a href="http://www.codepoet.org/andersen/erik/gpg.asc">public key</a>.
29
30<!--#include file="footer.html" -->
31
32
diff --git a/busybox/docs/busybox.net/docs.html b/busybox/docs/busybox.net/docs.html
deleted file mode 100644
index fc9ac6d2b..000000000
--- a/busybox/docs/busybox.net/docs.html
+++ /dev/null
@@ -1,27 +0,0 @@
1<!--#include file="header.html" -->
2
3
4<h3>Documentation</h3>
5Current documentation for BusyBox includes:
6
7<ul>
8 <li><a href=
9 "downloads/BusyBox.html">BusyBox.html</a>. This is a
10 list of the all the available commands in BusyBox
11 with complete usage information and examples of how
12 to use each app. I have spent a <em>lot</em> of time
13 updating these docs and trying to make them fairly
14 comprehensive. If you find any errors (factual,
15 grammatical, whatever) please let me know.</li>
16
17 <li><a href="downloads/README">README</a>. This is
18 the README file included in the busybox source
19 release.</li>
20
21 <li>If you need more help, the BusyBox <a href=
22 "lists/busybox/">mailing list</a> is a good place to
23 start.</li>
24</ul>
25
26<!--#include file="footer.html" -->
27
diff --git a/busybox/docs/busybox.net/download.html b/busybox/docs/busybox.net/download.html
deleted file mode 100644
index a6a86ac33..000000000
--- a/busybox/docs/busybox.net/download.html
+++ /dev/null
@@ -1,38 +0,0 @@
1<!--#include file="header.html" -->
2
3
4
5<h3>Download</h3>
6
7Source for the latest release can always be
8downloaded from <a href="downloads">http://www.busybox.net/downloads</a>.
9
10<p>
11You can also obtain <a href= "downloads/snapshots/">Daily Snapshots</a> of
12the latest stable, and the latest development CVS source trees.
13
14<p>
15BusyBox now has <b>two</b> CVS trees. The "busybox-stable" tree
16contains the older 0.60.x stable series. The "busybox" tree contains
17the latest 1.0.0-preX development version of busybox.<br>
18
19<ul>
20 <li> Click here to browse the <a href="/cgi-bin/cvsweb/busybox/">
21 CVS tree for the 1.0.0-preX development version of BusyBox</a>
22 </li>
23
24 <li>Click here to browse the <a href="/cgi-bin/cvsweb/busybox.stable/">
25 CVS tree for the stable 0.60.x version of BusyBox</a>.
26 </li>
27
28 <li>Anonymous <a href="cvs_anon.html">CVS access</a> is available.
29 </li>
30
31 <li>For those that are actively contributing there is
32 even <a href="cvs_write.html">CVS write access</a>.
33 </li>
34
35</ul>
36
37<!--#include file="footer.html" -->
38
diff --git a/busybox/docs/busybox.net/footer.html b/busybox/docs/busybox.net/footer.html
deleted file mode 100644
index 9756f5dde..000000000
--- a/busybox/docs/busybox.net/footer.html
+++ /dev/null
@@ -1,20 +0,0 @@
1<!-- Footer -->
2
3
4 </td>
5 </tr>
6 </table>
7
8<hr />
9
10 <p>
11 <font face="arial, helvetica, sans-serif" size="-1">
12 <a HREF="/copyright.txt">Copyright &copy; 1999-2003 Erik Andersen</a>
13 <br>
14 Mail all comments, insults, suggestions and bribes to
15 <br>
16 Erik Andersen <A HREF="mailto:andersen@codepoet.org">andersen@codepoet.org</A><BR>
17 </font>
18
19 </body>
20</html>
diff --git a/busybox/docs/busybox.net/header.html b/busybox/docs/busybox.net/header.html
deleted file mode 100644
index 77c141832..000000000
--- a/busybox/docs/busybox.net/header.html
+++ /dev/null
@@ -1,81 +0,0 @@
1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
2"http://www.w3.org/TR/REC-html40/loose.dtd">
3
4<html>
5 <head>
6 <title>BusyBox</title>
7 <style type="text/css">
8 body {
9 background-color: #DEE2DE;
10 color: #000000;
11 }
12 :link { color: #660000 }
13 :visited { color: #660000 }
14 :active { color: #660000 }
15 td.c2 {font-family: arial, helvetica, sans-serif; font-size: 80%}
16 td.c1 {font-family: lucida, helvetica; font-size: 248%}
17 </style>
18 </head>
19
20 <body>
21 <basefont face="lucida, helvetica, arial" size="3">
22
23
24
25
26<table border="0" cellpadding="0" cellspacing="0">
27
28
29<tr>
30<td>
31 <div class="c3">
32 <table border="0" cellspacing="1" cellpadding="2">
33 <tr>
34 <td class="c1">BUSYBOX</td>
35 </tr>
36 </table>
37 </div>
38
39 <a href="/"><IMG SRC="images/busybox1.png" alt="BusyBox" border="0"></a><BR>
40</td>
41</tr>
42
43<tr>
44
45<td valign="TOP">
46 <br><a href="/about.html">About</a>
47 <br><a href="/screenshot.html">Screenshot</a>
48 <br><a href="/lists.html">Mailing Lists</a>
49 <br><a href="/news.html">Latest News</a>
50 <br><a href="/download.html">Download</a>
51 <br><a href="/FAQ.html">FAQ</a>
52 <br><a href="/cvs_anon.html">Accessing CVS</a>
53 <br><a href="/cgi-bin/cvsweb/busybox/">Browse CVS</a>
54 <br><a href="/docs.html">Documentation</a>
55 <br><a href="/products.html">Products</a>
56 <br><a href="/shame.html">Hall of Shame</a>
57 <br><a href="/license.html">License</a>
58
59 <p><b>Related Sites</b>
60 <br><a href="http://uclibc.org/">uClibc.org</a>
61 <br><a href="http://udhcp.busybox.net/">udhcp</a>
62 <br><a href="http://tinylogin.busybox.net/">tinylogin</a>
63 <br><a href="http://www.ucdot.org/">uCdot</a>
64 <br><a href="http://www.linuxdevices.com">LinuxDevices</a>
65 <br><a href="http://slashdot.org/">Slashdot</a>
66 <br><a href="http://freshmeat.net/">Freshmeat</a>
67 <br><a href="http://linuxtoday.com/">Linux Today</a>
68 <br><a href="http://lwn.net/">Linux Weekly News</a>
69 <br><a href="http://www.tldp.org/HOWTO">Linux HOWTOs</a>
70
71<!--
72 <a href="http://validator.w3.org/check/referer"><img
73 src="/images/vh40.gif" height=31 width=88
74 align=left border=0 alt="Valid HTML 4.0!"></a>
75-->
76
77</td>
78
79
80<td Valign="TOP">
81
diff --git a/busybox/docs/busybox.net/images/back.png b/busybox/docs/busybox.net/images/back.png
deleted file mode 100644
index 79923869b..000000000
--- a/busybox/docs/busybox.net/images/back.png
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/images/busybox.jpeg b/busybox/docs/busybox.net/images/busybox.jpeg
deleted file mode 100644
index 37edc9614..000000000
--- a/busybox/docs/busybox.net/images/busybox.jpeg
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/images/busybox.png b/busybox/docs/busybox.net/images/busybox.png
deleted file mode 100644
index b1eb92f38..000000000
--- a/busybox/docs/busybox.net/images/busybox.png
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/images/busybox1.png b/busybox/docs/busybox.net/images/busybox1.png
deleted file mode 100644
index 4d3126a52..000000000
--- a/busybox/docs/busybox.net/images/busybox1.png
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/images/busybox2.jpg b/busybox/docs/busybox.net/images/busybox2.jpg
deleted file mode 100644
index abf8f0610..000000000
--- a/busybox/docs/busybox.net/images/busybox2.jpg
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/images/busybox3.jpg b/busybox/docs/busybox.net/images/busybox3.jpg
deleted file mode 100644
index 0fab84cf9..000000000
--- a/busybox/docs/busybox.net/images/busybox3.jpg
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/images/dir.png b/busybox/docs/busybox.net/images/dir.png
deleted file mode 100644
index 1d633ce4a..000000000
--- a/busybox/docs/busybox.net/images/dir.png
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/images/donate.png b/busybox/docs/busybox.net/images/donate.png
deleted file mode 100644
index b55621bb9..000000000
--- a/busybox/docs/busybox.net/images/donate.png
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/images/fm.mini.png b/busybox/docs/busybox.net/images/fm.mini.png
deleted file mode 100644
index c0883cd34..000000000
--- a/busybox/docs/busybox.net/images/fm.mini.png
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/images/gfx_by_gimp.png b/busybox/docs/busybox.net/images/gfx_by_gimp.png
deleted file mode 100644
index d58314034..000000000
--- a/busybox/docs/busybox.net/images/gfx_by_gimp.png
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/images/ltbutton2.png b/busybox/docs/busybox.net/images/ltbutton2.png
deleted file mode 100644
index 9bad9496a..000000000
--- a/busybox/docs/busybox.net/images/ltbutton2.png
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/images/sdsmall.png b/busybox/docs/busybox.net/images/sdsmall.png
deleted file mode 100644
index b1024501b..000000000
--- a/busybox/docs/busybox.net/images/sdsmall.png
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/images/text.png b/busybox/docs/busybox.net/images/text.png
deleted file mode 100644
index 6034f899f..000000000
--- a/busybox/docs/busybox.net/images/text.png
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/images/vh40.gif b/busybox/docs/busybox.net/images/vh40.gif
deleted file mode 100644
index c5e9402e7..000000000
--- a/busybox/docs/busybox.net/images/vh40.gif
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/images/written.in.vi.png b/busybox/docs/busybox.net/images/written.in.vi.png
deleted file mode 100644
index 84f59bc15..000000000
--- a/busybox/docs/busybox.net/images/written.in.vi.png
+++ /dev/null
Binary files differ
diff --git a/busybox/docs/busybox.net/index.html b/busybox/docs/busybox.net/index.html
deleted file mode 100644
index 1bab6b069..000000000
--- a/busybox/docs/busybox.net/index.html
+++ /dev/null
@@ -1 +0,0 @@
1<!--#include file="news.html" -->
diff --git a/busybox/docs/busybox.net/license.html b/busybox/docs/busybox.net/license.html
deleted file mode 100644
index 14324f1df..000000000
--- a/busybox/docs/busybox.net/license.html
+++ /dev/null
@@ -1,135 +0,0 @@
1<!--#include file="header.html" -->
2
3
4<h3>The GPL BusyBox license</h3>
5
6There has been some confusion in the past as to exactly what is
7required to safely distribute GPL'd software such as BusyBox as
8part of a product. To ensure that there is no confusion
9whatsoever, this page attempts to summarize what you should do to
10ensure you do not accidentally violate the law.
11
12<p>
13<h3>Complying with the BusyBox license is easy and completely free.</h3>
14
15U.S. and International Law protects copyright owners from the unauthorized
16reproduction, adaptation, display, distribution, etc of copyright protected
17works. Copyright violations (such as shipping BusyBox in a manner contrary to
18its license) are subject to severe penalties. The courts can award up to
19$150,000 per product shipped without even showing any actual loss by the
20copyright holder. Criminal penalties are available for intentional acts
21undertaken for purposes of "commercial advantage" or "private financial gain."
22In addition, if it comes to my attention that you are violating the BusyBox
23license, I will list you on the <a href="/shame.html">BusyBox Hall of Shame</a>
24webpage.
25
26<p>
27
28Nobody wants that to happen. Do everyone a favor and don't break the law -- if
29you use BusyBox, you <b>must comply with the BusyBox license</b>.
30
31<p>
32<h3>BusyBox is licensed under the GNU General Public License</h3>
33
34BusyBox is licensed under the GNU General Public License , which
35is generally just abbreviated as the GPL license, or
36just the GPL.
37<p>
38<a href="/products.html">Anyone thinking of shipping
39BusyBox as part of a product</a> should be familiar with the
40licensing terms under which they are allowed to use and
41distribute BusyBox. You are advised to take a look over the
42
43<ul>
44<li><a href="http://www.gnu.org/licenses/gpl.html">full text of
45the GNU General Public License</a>, and
46<li><a href="http://www.gnu.org/licenses/gpl-faq.html">
47Frequently Asked Questions about the GNU GPL</a>
48</ul>
49to be sure you (and your lawyers) fully understand them.
50
51<p>
52
53The following is a quick summary for the impatient. If you
54carefully follow these steps, it will ensure that you are 100%
55authorized to ship BusyBox with your product, and have no reason
56to worry about lawsuits or being listed on the <a
57href="/shame.html">BusyBox Hall of Shame</a> page. You will be
58able to sleep peacefully at night knowing you have fulfilled all
59your licensing obligations.
60
61<p>
62
63If you distribute a product, it should either be accompanied by
64<b>full source for all GPL'd products</b> (including BusyBox)
65and/or a <b>written offer</b> to supply the source for all
66GPL'd products for the cost of shipping and handling. The source
67has to be in its preferred machine readable form, so you cannot
68encrypt or obfuscate it. You are not required to provide full
69source for all the closed source applications that happen to be
70part of the system with BusyBox, though you can certainly do so
71if you feel like it. But providing source for the GPL licensed
72applications such as BusyBox is mandatory.
73
74<p>
75
76<b>Accompanied by source</b> generally means you distribute the full
77source code for all GPL'd products including BusyBox along with your
78product, such as by placing it somewhere on a driver CD. Full source
79code includes the BusyBox ".config" file used when your shipping BusyBox
80binary was compiled, and any and all modifications you made to the
81BusyBox source code.
82
83<p>
84
85<b>A written offer</b> generally means that somewhere in the
86documentation for your product, you write something like
87
88<blockquote>
89The GPL source code contained in this product is available as a
90free download from http://blah.blah.blah/
91</blockquote>
92Alternatively, you can offer the source code by writing
93somewhere in the documentation for your product something like
94<blockquote>
95If you would like a copy of the GPL source code contained in this
96product shipped to you on CD, please send $9.99 to &lt;address&gt;
97which covers the cost of preparing and mailing a CD to you.
98</blockquote>
99<p>
100
101Keep in mind though that if you distribute GPL'd binaries online (as is often
102done when supplying firmware updates), it is <b>highly</b> recommended that you
103make the corresponding source available online at the same place. Regardless,
104if you distribute a binary copy of BusyBox online (such as part of a firmware
105update) you <b>must</b> either make source available online (i.e.
106<b>accompanied by source</b>) and/or inform those downloading firmware updates
107of their right to obtain source (i.e. <b>a written offer</b>). Failure to do
108so is a violation of your licensing obligations.
109
110
111<p>
112
113Some people have the mistaken understanding that if they use unmodified
114GPL'd source code, they do not need to distribute anything. This belief
115is not correct, and is not supported by the
116<a href="http://www.gnu.org/licenses/gpl.html">text of GPL</a>.
117Please do re-read it -- you will find there is no such provision.
118If you distribute any GPL'd binaries, you must also make source available
119as discussed on this webpage.
120
121<p>
122<h3>A Good Example</h3>
123
124These days, <a href="http://www.linksys.com/">Linksys</a> is
125doing a good job at complying with the GPL, they get to be an
126example of how to do things right. Please take a moment and
127check out what they do with
128<a href="http://www.linksys.com/download/firmware.asp?fwid=178">
129distributing the firmware for their WRT54G Router.</a>
130Following their example would be a fine way to ensure that you
131have also fulfilled your licensing obligations.
132
133
134<!--#include file="footer.html" -->
135
diff --git a/busybox/docs/busybox.net/lists.html b/busybox/docs/busybox.net/lists.html
deleted file mode 100644
index 5c50c957c..000000000
--- a/busybox/docs/busybox.net/lists.html
+++ /dev/null
@@ -1,45 +0,0 @@
1<!--#include file="header.html" -->
2
3
4<!-- Begin Introduction section -->
5
6<h3>Mailing List Information</h3>
7BusyBox has a <a href="/lists/busybox/">mailing list</a> for discussion and
8development. You can subscribe by visiting
9<a href="http://codepoet.org/mailman/listinfo/busybox">this page</a>.
10Only subscribers to the BusyBox mailing list are allowed to post
11to this list.
12
13<p>
14There is also a mailing list for <a href="/lists/busybox-cvs/">active developers</a>
15wishing to read the complete diff of each and every change to busybox -- not for the
16faint of heart. Active developers can subscribe by visiting
17<a href="http://codepoet.org/mailman/listinfo/busybox-cvs">this page</a>.
18The CVS server is the only one permtted to post to this list.
19
20<p>
21
22
23<h3>Search the List Archives</h3>
24Please search the mailing list archives before asking questions on the mailing
25list, since there is a good chance someone else has asked the same question
26before. Checking the archives is a great way to avoid annoying everyone on the
27list with frequently asked questions...
28<p>
29
30<center>
31<form method="GET" action="http://www.google.com/custom">
32<input type="hidden" name="domains" value="busybox.net">
33<input type="hidden" name="sitesearch" value="busybox.net">
34<input type="text" name="q" size="31" maxlength="255" value="">
35<br>
36<input type="submit" name="sa" value="search the mailing list archives">
37<br>
38<a href="http://www.google.com"><img src="http://www.google.com/logos/Logo_25wht.gif" border="0" alt="Google" height="32" width="75" align="middle"></a>
39<br>
40</form>
41</center>
42
43
44
45<!--#include file="footer.html" -->
diff --git a/busybox/docs/busybox.net/news.html b/busybox/docs/busybox.net/news.html
deleted file mode 100644
index 0d4c81bab..000000000
--- a/busybox/docs/busybox.net/news.html
+++ /dev/null
@@ -1,52 +0,0 @@
1<!--#include file="header.html" -->
2
3
4<ul>
5
6 <li><b>13 October 2004 -- BusyBox 1.00 released</b><p>
7
8 When you take a careful look at nearly every embedded Linux device or
9 software distribution shipping today, you will find a copy of BusyBox.
10 With countless routers, set top boxes, wireless access points, PDAs, and
11 who knows what else, the future for Linux and BusyBox on embedded devices
12 is looking very bright.
13
14 <p>
15
16 It is therefore with great satisfaction that I declare each and every
17 device already shipping with BusyBox is now officially out of date.
18 The highly anticipated release of BusyBox 1.00 has arrived!
19
20 <p>
21
22 Over three years in development, BusyBox 1.00 represents a tremendous
23 improvement over the old 0.60.x stable series. Now featuring a Linux
24 KernelConf based configuration system (as used by the Linux kernel),
25 Linux 2.6 kernel support, many many new applets, and the development
26 work and testing of thousands of people from around the world.
27
28 <p>
29
30 If you are already using BusyBox, you are strongly encouraged to upgrade to
31 BusyBox 1.00. If you are considering developing an embedded Linux device
32 or software distribution, you may wish to investigate if using BusyBox is
33 right for your application. If you need help getting started using
34 BusyBox, if you wish to donate to help cover expenses, or if you find a bug
35 and need help reporting it, you are invited to visit the <a
36 href="FAQ.html">BusyBox FAQ</a>.
37
38 <p>
39
40 As usual you can <a href="downloads">download busybox here</a>.
41
42 <p>Have Fun!
43
44 <p>
45 <li><b>Old News</b><p>
46 <a href="/oldnews.html">Click here to read older news</a>
47
48
49</ul>
50
51<!--#include file="footer.html" -->
52
diff --git a/busybox/docs/busybox.net/oldnews.html b/busybox/docs/busybox.net/oldnews.html
deleted file mode 100644
index 83987ecf8..000000000
--- a/busybox/docs/busybox.net/oldnews.html
+++ /dev/null
@@ -1,1060 +0,0 @@
1<!--#include file="header.html" -->
2
3
4<ul>
5
6 <li><b>16 August 2004 -- BusyBox 1.0.0-rc3 released</b><p>
7
8 Here goes release candidate 3...
9 <p>
10 The <a href="downloads/Changelog">changelog</a> has all the details.
11 And as usual you can <a href="downloads">download busybox here</a>.
12
13 <p>Have Fun!
14
15 <p>
16 <li><b>26 July 2004 -- BusyBox 1.0.0-rc2 released</b><p>
17
18 Here goes release candidate 2...
19 <p>
20 The <a href="downloads/Changelog">changelog</a> has all the details.
21 And as usual you can <a href="downloads">download busybox here</a>.
22
23 <p>Have Fun!
24
25 <p>
26 <li><b>20 July 2004 -- BusyBox 1.0.0-rc1 released</b><p>
27
28 Here goes release candidate 1... This fixes all (most?) of the problems
29 that have turned up since -pre10. In particular, loading and unloading of
30 kernel modules with 2.6.x kernels should be working much better.
31 <p>
32
33 I <b>really</b> want to get BusyBox 1.0.0 released soon and I see no real
34 reason why the 1.0.0 release shouldn't happen with things pretty much as
35 is. BusyBox is in good shape at the moment, and it works nicely for
36 everything that I'm doing with it. And from the reports I've been getting,
37 it works nicely for what most everyone else is doing with it as well.
38 There will eventually be a 1.0.1 anyway, so we might as well get on with
39 it. No, BusyBox is not perfect. No piece of software ever is. And while
40 there is still plenty that can be done to improve things, most of that work
41 is waiting till we can get a solid 1.0.0 release out the door....
42 <p>
43
44 Please do not bother to send in patches adding cool new features at this
45 time. Only bug-fix patches will be accepted. If you have submitted a
46 bug-fixing patch to the busybox mailing list and no one has emailed you
47 explaining why your patch was rejected, it is safe to say that your patch
48 has been lost or forgotten. That happens sometimes. Please re-submit your
49 bug-fixing patch to the BusyBox mailing list, and be sure to put "[PATCH]"
50 at the beginning of the email subject line!
51
52 <p>
53 The <a href="downloads/Changelog">changelog</a> has all the details.
54 And as usual you can <a href="downloads">download busybox here</a>.
55
56 <p>Have Fun!
57
58 <p>
59 On a less happy note, My 92 year old grandmother (my dad's mom) passed away
60 yesterday (June 19th). The funeral will be Thursday in a little town about
61 2 hours south of my home. I've checked and there is absolutely no way I
62 could be back in time for the funeral if I attend <a
63 href="http://www.linuxsymposium.org/2004/">OLS</a> and give my presentation
64 as scheduled.
65 <p>
66 As such, it is with great reluctance and sadness that I have come
67 to the conclusion I will have to make my appologies and skip OLS
68 this year.
69 <p>
70
71
72 <p>
73 <li><b>13 April 2004 -- BusyBox 1.0.0-pre10 released</b><p>
74
75 Ok, I lied. It turns out that -pre9 will not be the final BusyBox
76 pre-release. With any luck however -pre10 will be, since I <b>really</b>
77 want to get BusyBox 1.0.0 released very soon. As usual, please do not
78 bother to send in patches adding cool new features at this time. Only
79 bug-fix patches will be accepted. It would also be <b>very</b> helpful if
80 people could continue to review the BusyBox documentation and submit
81 improvements.
82
83 <p>
84 The <a href="downloads/Changelog">changelog</a> has all the details.
85 And as usual you can <a href="downloads">download busybox here</a>.
86
87 <p>Have Fun!
88 <p>
89
90
91 <p>
92 <li><b>6 April 2004 -- BusyBox 1.0.0-pre9 released</b><p>
93
94 Here goes the final BusyBox pre-release... This is your last chance for
95 bug fixes. With luck this will be released as BusyBox 1.0.0 later this
96 week. Please do not bother to send in patches adding cool new features at
97 this time. Only bug-fix patches will be accepted. It would also be
98 <b>very</b> helpful if people could help review the BusyBox documentation
99 and submit improvements. I've spent a lot of time updating the
100 documentation to make it better match reality, but I could really use some
101 assistance in checking that the features supported by the various applets
102 match the features listed in the documentation.
103
104 <p>
105 I had hoped to get this released a month ago, but
106 <a href="http://codepoet.org/gallery/baby_peter/img_1796">
107 another release on 1 March 2004</a> has kept me busy...
108
109 <p>
110 The <a href="downloads/Changelog">changelog</a> has all the details.
111 And as usual you can <a href="downloads">download busybox here</a>.
112
113 <p>Have Fun!
114 <p>
115
116
117 <p>
118 <li><b>23 February 2004 -- BusyBox 1.0.0-pre8 released</b><p>
119
120 Here goes yet another BusyBox pre-release... Please do not bother to send
121 in patches supplying new features at this time. Only bug-fix patches will
122 be accepted. If you have a cool new feature you would like to see
123 supported, or if you have an amazing new applet you would like to submit,
124 please wait and submit such things later. We really want to get a release
125 out we can all be proud of. We are still aiming to finish off the -pre
126 series in February and move on to the final 1.0.0 release... So if you
127 spot any bugs, now would be an excellent time to send in a fix to the
128 busybox mailing list. It would also be <b>very</b> helpful if people could
129 help review the BusyBox documentation and submit improvements. It would be
130 especially helpful if people could check that the features supported by the
131 various applets match the features listed in the documentation.
132
133 <p>
134
135 The <a href="downloads/Changelog">changelog</a> has all the details.
136 And as usual you can <a href="downloads">download busybox here</a>.
137
138 <p>Have Fun!
139 <p>
140
141
142 <li><b>4 February 2004 -- BusyBox 1.0.0-pre7 released</b><p>
143
144 There was a bug in -pre6 that broke argument parsing for a
145 number of applets, since a variable was not being zeroed out
146 properly. This release is primarily intended to fix that one
147 problem. In addition, this release fixes several other
148 problems, including a rewrite by mjn3 of the code for parsing
149 the busybox.conf file used for suid handling, some shell updates
150 from vodz, and a scattering of other small fixes. We are still
151 aiming to finish off the -pre series in February and move on to
152 the final 1.0.0 release... If you see any problems, of have
153 suggestions to make, as always, please feel free to email the
154 busybox mailing list.
155
156 <p>
157
158 The <a href="downloads/Changelog">changelog</a> has all
159 the details. And as usual you can
160 <a href="downloads">download busybox here</a>.
161
162 <p>Have Fun!
163 <p>
164
165
166 <p>
167 <li><b>30 January 2004 -- BusyBox 1.0.0-pre6 released</b><p>
168
169 Here goes the next pre-release for the new BusyBox stable
170 series. This release adds a number of size optimizations,
171 updates udhcp, fixes up 2.6 modutils support, updates ash
172 and the shell command line editing, and the usual pile of
173 bug fixes both large and small. Things appear to be
174 settling down now, so with a bit of luck and some testing
175 perhaps we can finish off the -pre series in February and
176 move on to the final 1.0.0 release... If you see any
177 problems, of have suggestions to make, as always, please
178 feel free to email the busybox mailing list.
179
180 <p>
181
182 People who rely on the <a href= "downloads/snapshots/">daily BusyBox snapshots</a>
183 should be aware that snapshots of the old busybox 0.60.x
184 series are no longer available. Daily snapshots are now
185 only available for the BusyBox 1.0.0 series and now use
186 the naming scheme "busybox-&lt;date&gt;.tar.bz2". Please
187 adjust any build scripts using the old naming scheme accordingly.
188
189 <p>
190
191 The <a href="downloads/Changelog">changelog</a> has all
192 the details. And as usual you can
193 <a href="downloads">download busybox here</a>.
194
195 <p>Have Fun!
196 <p>
197
198
199 <p>
200 <li><b>23 December 2003 -- BusyBox 1.0.0-pre5 released</b><p>
201
202 Here goes the next pre-release for the new BusyBox stable
203 series. The most obvious thing in this release is a fix for
204 a terribly stupid bug in mount that prevented it from working
205 properly unless you specified the filesystem type. This
206 release also fixes a few compile problems, updates udhcp,
207 fixes a silly bug in fdisk, fixes ifup/ifdown to behave like
208 the Debian version, updates devfsd, updates the 2.6.x
209 modutils support, add a new 'rx' applet, removes the obsolete
210 'loadacm' applet, fixes a few tar bugs, fixes a sed bug, and
211 a few other odd fixes.
212
213 <p>
214
215 If you see any problems, of have suggestions to make, as
216 always, please feel free to send an email to the busybox
217 mailing list.
218
219 <p>
220
221 The <a href="downloads/Changelog">changelog</a> has all
222 the details. And as usual you can
223 <a href="downloads">download busybox here</a>.
224
225 <p>Have Fun!
226 <p>
227
228
229
230 <li><b>10 December 2003 -- BusyBox 1.0.0-pre4 released</b><p>
231
232 Here goes the fourth pre-release for the new BusyBox stable
233 series. This release includes major rework to sed, lots of
234 rework on tar, a new tiny implementation of bunzip2, a new
235 devfsd applet, support for 2.6.x kernel modules, updates to
236 the ash shell, sha1sum and md5sum have been merged into a
237 common applet, the dpkg applets has been cleaned up, and tons
238 of random bugs have been fixed. Thanks everyone for all the
239 testing, bug reports, and patches! Once again, a big
240 thank-you goes to Glenn McGrath (bug1) for stepping in and
241 helping get patches merged!
242
243 <p>
244
245 And of course, if you are reading this, you might have noticed
246 the busybox website has been completely reworked. Hopefully
247 things are now somewhat easier to navigate... If you see any
248 problems, of have suggestions to make, as always, please feel
249 free to send an email to the busybox mailing list.
250
251 <p>
252
253 The <a href="downloads/Changelog">changelog</a> has all
254 the details. And as usual you can
255 <a href="downloads">download busybox here</a>.
256
257 <p>Have Fun!
258
259
260
261 <p>
262 <li><b>12 Sept 2003 -- BusyBox 1.0.0-pre3 released</b><p>
263
264 Here goes the third pre-release for the new BusyBox stable
265 series. The last prerelease has held up quite well under
266 testing, but a number of problems have turned up as the number
267 of people using it has increased. Thanks everyone for all
268 the testing, bug reports, and patches!
269
270 <p>
271
272 If you have submitted a patch or a bug report to the busybox
273 mailing list and no one has emailed you explaining why your
274 patch was rejected, it is safe to say that your patch has
275 somehow gotten lost or forgotten. That happens sometimes.
276 Please re-submit your patch or bug report to the BusyBox
277 mailing list!
278
279 <p>
280
281 The point of the "-preX" versions is to get a larger group of
282 people and vendors testing, so any problems that turn up can be
283 fixed prior to the final 1.0.0 release. The main feature
284 (besides additional testing) that is still still on the TODO
285 list before the final BusyBox 1.0.0 release is sorting out the
286 modutils issues. For the new 2.6.x kernels, we already have
287 patches adding insmod and rmmod support and those need to be
288 integrated. For 2.4.x kernels, for which busybox only supports
289 a limited number of architectures, we may want to invest a bit
290 more work before we cut 1.0.0. Or we may just leave 2.4.x
291 module loading alone.
292
293 <p>
294
295 I had hoped this release would be out a month ago. And of
296 course, it wasn't since Erik became busy getting a release of
297 <a href="http://www.uclibc.org/">uClibc</a>
298 out the door. Many thanks to Glenn McGrath (bug1) for
299 stepping in and helping get a bunch of patches merged! I am
300 not even going to state a date for releasing BusyBox 1.0.0
301 -pre4 (or the final 1.0.0). We're aiming for late September...
302 But if this release proves as to be exceptionally stable (or
303 exceptionally unstable!), the next release may be very soon
304 indeed.
305
306 <p>
307
308 The <a href="downloads/Changelog">changelog</a> has all
309 the details. And as usual you can
310 <a href="downloads">download busybox here</a>.
311
312 <p>Have Fun!
313
314
315 <p>
316 <li><b>30 July 2003 -- BusyBox 1.0.0-pre2 released</b><p>
317
318 Here goes another pre release for the new BusyBox stable
319 series. The last prerelease (pre1) was given quite a lot of
320 testing (thanks everyone!) which has helped turn up a number of
321 bugs, and these problems have now been fixed.
322
323 <p>
324
325 Highlights of -pre2 include updating the 'ash' shell to sync up
326 with the Debian 'dash' shell, a new 'hdparm' applet was added,
327 init again supports pivot_root, The 'reboot' 'halt' and
328 'poweroff' applets can now be used without using busybox init.
329 an ifconfig buffer overflow was fixed, losetup now allows
330 read-write loop devices, uClinux daemon support was added, the
331 'watchdog', 'fdisk', and 'kill' applets were rewritten, there were
332 tons of doc updates, and there were many other bugs fixed.
333 <p>
334
335 If you have submitted a patch and it is not included in this
336 release and Erik has not emailed you explaining why your patch
337 was rejected, it is safe to say that he has lost your patch.
338 That happens sometimes. Please re-submit your patch to the
339 BusyBox mailing list.
340 <p>
341
342 The point of the "-preX" versions is to get a larger group of
343 people and vendors testing, so any problems that turn up can be
344 fixed prior to the final 1.0.0 release. The main feature that
345 is still still on the TODO list before the final BusyBox 1.0.0
346 release is adding module support for the new 2.6.x kernels. If
347 necessary, a -pre3 BusyBox release will happen on August 6th.
348 Hopefully (i.e. unless some horrible catastrophic problem
349 turns up) the final BusyBox 1.0.0 release will be ready by
350 then...
351 <p>
352
353 The <a href="downloads/Changelog">changelog</a> has all
354 the details. As usual you can <a href="downloads">download busybox here</a>.
355
356 <p>Have Fun!
357 <p>
358
359 <p>
360 <li><b>15 July 2003 -- BusyBox 1.0.0-pre1 released</b><p>
361
362 The busybox development series has been under construction for
363 nearly two years now. Which is just entirely too long... So
364 it is with great pleasure that I announce the imminent release
365 of a new stable series. Due to the huge number of changes
366 since the last stable release (and the usual mindless version
367 number inflation) I am branding this new stable series verison
368 1.0.x...
369 <p>
370
371 The point of "-preX" versions is to get a larger group of
372 people and vendors testing, so any problems that turn up can be
373 fixed prior to the magic 1.0.0 release (which should happen
374 later this month)... I plan to release BusyBox 1.0.0-pre2 next
375 Monday (July 21st), and, if necessary, -pre3 on July 28th.
376 Hopefully (i.e. unless some horrible catastrophic problem turns
377 up) the final BusyBox 1.0.0 release should be ready by the end
378 of July.
379 <p>
380
381 If you have submitted patches, and they are not in this release
382 and I have not emailed you explaining why your patch was
383 rejected, it is safe to say that I have lost your patch. That
384 happens sometimes. Please do <B>NOT</b> send all your patches,
385 support questions, etc, directly to Erik. I get hundreds of
386 emails every day (which is why I end up losing patches
387 sometimes in the flood)... The busybox mailing list is the
388 right place to send your patches, support questions, etc.
389 <p>
390
391 I would like to especially thank Vladimir Oleynik (vodz), Glenn
392 McGrath (bug1), Robert Griebl (sandman), and Manuel Novoa III
393 (mjn3) for their significant efforts and contributions that
394 have made this release possible.
395 <p>
396
397 As usual you can <a href="downloads">download busybox here</a>.
398 You don't really need to bother with the
399 <a href="downloads/Changelog">changelog</a>, as the changes
400 vs the stable version are way too extensive to easily enumerate.
401 But you can take a look if you really want too.
402
403 <p>Have Fun!
404 <p>
405
406
407
408 <p>
409 <li><b>26 October 2002 -- BusyBox 0.60.5 released</b><p>
410
411 I am very pleased to announce that the BusyBox 0.60.5 (stable)
412 is now available for download. This is a bugfix release for
413 the stable series to address all the problems that have turned
414 up since the last release. Unfortunately, the previous release
415 had a few nasty bugs (i.e. init could deadlock, gunzip -c tried
416 to delete source files, cp -a wouldn't copy symlinks, and init
417 was not always providing controlling ttys when it should have).
418 I know I said that the previous release would be the end of the
419 0.60.x series. Well, it turns out I'm a liar. But this time I
420 mean it (just like last time ;-). This will be the last
421 release for the 0.60.x series -- all further development work
422 will be done for the development busybox tree. Expect the development
423 version to have its first real release very very soon now...
424
425 <p>
426 The <a href="downloads/Changelog.full">changelog</a> has all
427 the details. As usual you can <a href="downloads">download busybox here</a>.
428 <p>Have Fun!
429 <p>
430
431 <p>
432 <li><b>18 September 2002 -- BusyBox 0.60.4 released</b><p>
433
434 I am very pleased to announce that the BusyBox 0.60.4
435 (stable) is now available for download. This is primarily
436 a bugfix release for the stable series to address all
437 the problems that have turned up since the last
438 release. This will be the last release for the 0.60.x series.
439 I mean it this time -- all further development work will be done
440 on the development busybox tree, which is quite solid now and
441 should soon be getting its first real release.
442
443 <p>
444 The <a href="downloads/Changelog.full">changelog</a> has all
445 the details. As usual you can <a href="downloads">download busybox here</a>.
446 <p>Have Fun!
447 <p>
448
449
450 <p>
451 <li><b>27 April 2002 -- BusyBox 0.60.3 released</b><p>
452
453 I am very pleased to announce that the BusyBox 0.60.3 (stable) is
454 now available for download. This is primarily a bugfix release
455 for the stable series. A number of problems have turned up since
456 the last release, and this should address most of those problems.
457 This should be the last release for the 0.60.x series. The
458 development busybox tree has been progressing nicely, and will
459 hopefully be ready to become the next stable release.
460
461 <p>
462 The <a href="downloads/Changelog">changelog</a> has all
463 the details. As usual you can <a href="downloads">download busybox here</a>.
464 <p>Have Fun!
465 <p>
466
467
468 <p>
469 <li><b>6 March 2002 -- busybox.net now has mirrors!</b><p>
470
471 Busybox.net is now much more available, thanks to
472 the fine folks at <a href= "http://i-netinnovations.com/">http://i-netinnovations.com/</a>
473 who are providing hosting for busybox.net and
474 uclibc.org. In addition, we now have two mirrors:
475 <a href= "http://busybox.linuxmagic.com/">http://busybox.linuxmagic.com/</a>
476 in Canada and
477 <a href= "http://busybox.csservers.de/">http://busybox.csservers.de/</a>
478 in Germany. I hope this makes things much more
479 accessible for everyone!
480
481
482<li>
483<b>3 January 2002 -- Welcome to busybox.net!</b>
484
485<p>Thanks to the generosity of a number of busybox
486users, we have been able to purchase busybox.net
487(which is where you are probably reading this).
488Right now, busybox.net and uclibc.org are both
489living on my home system (at the end of my DSL
490line). I apologize for the abrupt move off of
491busybox.lineo.com. Unfortunately, I no longer have
492the access needed to keep that system updated (for
493example, you might notice the daily snapshots there
494stopped some time ago).</p>
495
496<p>Busybox.net is currently hosted on my home
497server, at the end of a DSL line. Unfortunately,
498the load on them is quite heavy. To address this,
499I'm trying to make arrangements to get busybox.net
500co-located directly at an ISP. To assist in the
501co-location effort, <a href=
502"http://www.codepoet.org/~markw">Mark Whitley</a>
503(author of busybox sed, cut, and grep) has donated
504his <a href=
505"http://www.netwinder.org/">NetWinder</a> computer
506for hosting busybox.net and uclibc.org. Once this
507system is co-located, the current speed problems
508should be completely eliminated. Hopefully, too,
509some of you will volunteer to set up some mirror
510sites, to help to distribute the load a bit.</p>
511
512<p><!--
513 <center>
514 Click here to help support busybox.net!
515 <form action="https://www.paypal.com/cgi-bin/webscr" method="post">
516 <input type="hidden" name="cmd" value="_xclick">
517 <input type="hidden" name="business" value="andersen@codepoet.org">
518 <input type="hidden" name="item_name" value="Support Busybox">
519 <input type="hidden" name="image_url" value="https://codepoet-consulting.com/images/busybox2.jpg">
520 <input type="hidden" name="no_shipping" value="1">
521 <input type="image" src="images/donate.png" border="0" name="submit" alt="Make donation using PayPal">
522 </form>
523 </center>
524 -->
525 Since some people expressed concern over BusyBox
526donations, let me assure you that no one is getting
527rich here. All BusyBox and uClibc donations will be
528spent paying for bandwidth and needed hardware
529upgrades. For example, Mark's NetWinder currently
530has just 64Meg of memory. As demonstrated when
531google spidered the site the other day, 64 Megs in
532not enough, so I'm going to be ordering 256Megs of
533ram and a larger hard drive for the box today. So
534far, donations received have been sufficient to
535cover almost all expenses. In the future, we may
536have co-location fees to worry about, but for now
537we are ok. A <b>HUGE thank-you</b> goes out to
538everyone that has contributed!<br>
539 -Erik</p>
540</li>
541
542<li>
543<b>20 November 2001 -- BusyBox 0.60.2 released</b>
544
545<p>We am very pleased to announce that the BusyBox
5460.60.2 (stable) is now released to the world. This
547one is primarily a bugfix release for the stable
548series, and it should take care of most everyone's
549needs till we can get the nice new stuff we have
550been working on in CVS ready to release (with the
551wonderful new buildsystem). The biggest change in
552this release (beyond bugfixes) is the fact that msh
553(the minix shell) has been re-worked by Vladimir N.
554Oleynik (vodz) and so it no longer crashes when
555told to do complex things with backticks.</p>
556
557<p>This release has been tested on x86, ARM, and
558powerpc using glibc 2.2.4, libc5, and uClibc, so it
559should work with just about any Linux system you
560throw it at. See the <a href=
561"downloads/Changelog">changelog</a> for <small>most
562of</small> the details. The last release was
563<em>very</em> solid for people, and this one should
564be even better.</p>
565
566<p>As usual BusyBox 0.60.2 can be downloaded from
567<a href=
568"downloads">http://www.busybox.net/downloads</a>.</p>
569
570<p>Have Fun.<br>
571 -Erik</p>
572</li>
573
574<li> <b>18 November 2001 -- Help us buy busybox.net!</b>
575
576<!-- Begin PayPal Logo -->
577<center>
578Click here to help buy busybox.net!
579<form action="https://www.paypal.com/cgi-bin/webscr" method="post">
580<input type="hidden" name="cmd" value="_xclick">
581<input type="hidden" name="business" value="andersen@codepoet.org">
582<input type="hidden" name="item_name" value="Support Busybox">
583<input type="hidden" name="image_url" value="https://busybox.net/images/busybox2.jpg">
584<input type="hidden" name="no_shipping" value="1">
585<input type="image" src="images/donate.png" border="0" name="submit" alt="Make donation using PayPal">
586</form>
587</center>
588<!-- End PayPal Logo -->
589
590I've contacted the current owner of busybox.net and he is willing
591to sell the domain name -- for $250. He also owns busybox.org but
592will not part with it... I will then need to pay the registry fee
593for a couple of years and start paying for bandwidth, so this will
594initially cost about $300. I would like to host busybox.net on my
595home machine (codepoet.org) so I have full control over the system,
596but to do that would require that I increase the level of bandwidth
597I am paying for. Did you know that so far this month, there
598have been over 1.4 Gigabytes of busybox ftp downloads? I don't
599even <em>know</em> how much CVS bandwidth it requires. For the
600time being, Lineo has continued to graciously provide this
601bandwidth, despite the fact that I no longer work for them. If I
602start running this all on my home machine, paying for the needed bandwidth
603will start costing some money.
604<p>
605
606I was going to pay it all myself, but my wife didn't like that
607idea at all (big surprise). It turns out &lt;insert argument
608where she wins and I don't&gt; she has better ideas
609about what we should spend our money on that don't involve
610busybox. She suggested I should ask for contributions on the
611mailing list and web page. So...
612<p>
613
614I am hoping that if everyone could contribute a bit, we could pick
615up the busybox.net domain name and cover the bandwidth costs. I
616know that busybox is being used by a lot of companies as well as
617individuals -- hopefully people and companies that are willing to
618contribute back a bit. So if everyone could please help out, that
619would be wonderful!
620<p>
621
622
623<li> <b>23 August 2001 -- BusyBox 0.60.1 released</b>
624<br>
625
626 This is a relatively minor bug fixing release that fixes
627 up the bugs that have shown up in the stable release in
628 the last few weeks. Fortunately, nothing <em>too</em>
629 serious has shown up. This release only fixes bugs -- no
630 new features, no new applets. So without further ado,
631 here it is. Come and get it.
632 <p>
633 The
634 <a href="downloads/Changelog">changelog</a> has all
635 the details. As usual BusyBox 0.60.1 can be downloaded from
636 <a href="downloads">http://busybox.net/downloads</a>.
637 <p>Have Fun!
638 <p>
639
640
641<li> <b>2 August 2001 -- BusyBox 0.60.0 released</b>
642<br>
643 I am very pleased to announce the immediate availability of
644 BusyBox 0.60.0. I have personally tested this release with libc5, glibc,
645 and <a href="http://uclibc.org/">uClibc</a> on
646 x86, ARM, and powerpc using linux 2.2 and 2.4, and I know a number
647 of people using it on everything from ia64 to m68k with great success.
648 Everything seems to be working very nicely now, so getting a nice
649 stable bug-free(tm) release out seems to be in order. This releases fixes
650 a memory leak in syslogd, a number of bugs in the ash and msh shells, and
651 cleans up a number of things.
652
653 <p>
654
655 Those wanting an easy way to test the 0.60.0 release with uClibc can
656 use <a href="http://user-mode-linux.sourceforge.net/">User-Mode Linux</a>
657 to give it a try by downloading and compiling
658 <a href="ftp://busybox.net/buildroot.tar.gz">buildroot.tar.gz</a>.
659 You don't have to be root or reboot your machine to run test this way.
660 Preconfigured User-Mode Linux kernel source is also on busybox.net.
661 <p>
662 Another cool thing is the nifty <a href="downloads/tutorial/index.html">
663 BusyBox Tutorial</a> contributed by K Computing. This requires
664 a ShockWave plugin (or standalone viewer), so you may want to grab the
665 the GPLed shockwave viewer from <a href="http://www.swift-tools.com/Flash/flash-0.4.10.tgz">here</a>
666 to view the tutorial.
667 <p>
668
669 Finally, In case you didn't notice anything odd about the
670 version number of this release, let me point out that this release
671 is <em>not</em> 0.53, because I bumped the version number up a
672 bit. This reflects the fact that this release is intended to form
673 a new stable BusyBox release series. If you need to rely on a
674 stable version of BusyBox, you should plan on using the stable
675 0.60.x series. If bugs show up then I will release 0.60.1, then
676 0.60.2, etc... This is also intended to deal with the fact that
677 the BusyBox build system will be getting a major overhaul for the
678 next release and I don't want that to break products that people
679 are shipping. To avoid that, the new build system will be
680 released as part of a new BusyBox development series that will
681 have some not-yet-decided-on odd version number. Once things
682 stabilize and the new build system is working for everyone, then
683 I will release that as a new stable release series.
684
685 <p>
686 The
687 <a href="downloads/Changelog">changelog</a> has all
688 the details. As usual BusyBox 0.60.0 can be downloaded from
689 <a href="downloads">http://busybox.net/downloads</a>.
690 <p>Have Fun!
691 <p>
692
693
694<li> <b>7 July 2001 -- BusyBox 0.52 released</b>
695<br>
696
697 I am very pleased to announce the immediate availability of
698 BusyBox 0.52 (the "new-and-improved rock-solid release"). This
699 release is the result of <em>many</em> hours of work and has tons
700 of bugfixes, optimizations, and cleanups. This release adds
701 several new applets, including several new shells (such as hush, msh,
702 and ash).
703
704 <p>
705 The
706 <a href="downloads/Changelog">changelog</a> covers
707 some of the more obvious details, but there are many many things that
708 are not mentioned, but have been improved in subtle ways. As usual,
709 BusyBox 0.52 can be downloaded from
710 <a href="downloads">http://busybox.net/downloads</a>.
711 <p>Have Fun!
712 <p>
713
714
715<li> <b>10 April 2001 - Graph of Busybox Growth </b>
716<br>
717The illustrious Larry Doolittle has made a PostScript chart of the growth
718of the Busybox tarball size over time. It is available for downloading /
719viewing <a href= "busybox-growth.ps"> right here</a>.
720
721<p> (Note that while the number of applets in Busybox has increased, you
722can still configure Busybox to be as small as you want by selectively
723turning off whichever applets you don't need.)
724<p>
725
726
727<li> <b>10 April 2001 -- BusyBox 0.51 released</b>
728<br>
729
730 BusyBox 0.51 (the "rock-solid release") is now out there. This
731 release adds only 2 new applets: env and vi. The vi applet,
732 contributed by Sterling Huxley, is very functional, and is only
733 22k. This release fixes 3 critical bugs in the 0.50 release.
734 There were 2 potential segfaults in lash (the busybox shell) in
735 the 0.50 release which are now fixed. Another critical bug in
736 0.50 which is now fixed: syslogd from 0.50 could potentially
737 deadlock the init process and thereby break your entire system.
738 <p>
739
740 There are a number of improvements in this release as well. For
741 one thing, the wget applet is greatly improved. Dmitry Zakharov
742 added FTP support, and Laurence Anderson make wget fully RFC
743 compliant for HTTP 1.1. The mechanism for including utility
744 functions in previous releases was clumsy and error prone. Now
745 all utility functions are part of a new libbb library, which makes
746 maintaining utility functions much simpler. And BusyBox now
747 compiles on itanium systems (thanks to the Debian itanium porters
748 for letting me use their system!).
749 <p>
750 You can read the
751 <a href="downloads/Changelog">changelog</a> for
752 complete details. BusyBox 0.51 can be downloaded from
753 <a href="downloads">http://busybox.net/downloads</a>.
754 <p>Have Fun!
755 <p>
756
757<li> <b>Busybox Boot-Floppy Image</b>
758
759<p>Because you asked for it, we have made available a <a href=
760"downloads/busybox.floppy.img"> Busybox boot floppy
761image</a>. Here's how you use it:
762
763<ol>
764
765 <li> <a href= "downloads/busybox.floppy.img">
766 Download the image</a>
767
768 <li> dd it onto a floppy like so: <tt> dd if=busybox.floppy.img
769 of=/dev/fd0 ; sync </tt>
770
771 <li> Pop it in a machine and boot up.
772
773</ol>
774
775<p> If you want to look at the contents of the initrd image, do this:
776
777<pre>
778 mount ./busybox.floppy.img /mnt -o loop -t msdos
779 cp /mnt/initrd.gz /tmp
780 umount /mnt
781 gunzip /tmp/initrd.gz
782 mount /tmp/initrd /mnt -o loop -t minix
783</pre>
784
785
786<li> <b>15 March 2001 -- BusyBox 0.50 released</b>
787<br>
788
789 This release adds several new applets including ifconfig, route, pivot_root, stty,
790 and tftp, and also fixes tons of bugs. Tab completion in the
791 shell is now working very well, and the shell's environment variable
792 expansion was fixed. Tons of other things were fixed or made
793 smaller. For a fairly complete overview, see the
794 <a href="downloads/Changelog">changelog</a>.
795 <p>
796 lash (the busybox shell) is still with us, fixed up a bit so it
797 now behaves itself quite nicely. It really is quite usable as
798 long as you don't expect it to provide Bourne shell grammer.
799 Standard things like pipes, redirects, command line editing, and
800 environment variable expansion work great. But we have found that
801 this shell, while very usable, does not provide an extensible
802 framework for adding in full Bourne shell behavior. So the first order of
803 business as we begin working on the next BusyBox release will be to merge in the new shell
804 currently in progress at
805 <a href="http://doolittle.faludi.com/~larry/parser.html">Larry Doolittle's website</a>.
806 <p>
807
808
809<li> <b>27 January 2001 -- BusyBox 0.49 released</b>
810<br>
811
812 Several new applets, lots of bug fixes, cleanups, and many smaller
813 things made nicer. Several cleanups and improvements to the shell.
814 For a list of the most interesting changes
815 you might want to look at the <a href="downloads/Changelog">changelog</a>.
816 <p>
817 Special thanks go out to Matt Kraai and Larry Doolittle for all their
818 work on this release, and for keeping on top of things while I've been
819 out of town.
820 <p>
821 <em>Special Note</em><br>
822
823 BusyBox 0.49 was supposed to have replaced lash, the BusyBox
824 shell, with a new shell that understands full Bourne shell/Posix shell grammer.
825 Well, that simply didn't happen in time for this release. A new
826 shell that will eventually replace lash is already under
827 construction. This new shell is being developed by Larry
828 Doolittle, and could use all of our help. Please see the work in
829 progress on <a href="http://doolittle.faludi.com/~larry/parser.html">Larry's website</a>
830 and help out if you can. This shell will be included in the next
831 release of BusyBox.
832 <p>
833
834<li> <b>13 December 2000 -- BusyBox 0.48 released</b>
835<br>
836
837 This release fixes lots and lots of bugs. This has had some very
838 rigorous testing, and looks very, very clean. The usual tar
839 update of course: tar no longer breaks hardlinks, tar -xzf is
840 optionally supported, and the LRP folks will be pleased to know
841 that 'tar -X' and 'tar --exclude' are both now in. Applets are
842 now looked up using a binary search making lash (the busybox
843 shell) much faster. For the new debian-installer (for Debian
844 woody) a .udeb can now be generated.
845 <p>
846 The curious can get a list of some of the more interesting changes by reading
847 the <a href="downloads/Changelog">changelog</a>.
848 <p>
849 Many thanks go out to the many many people that have contributed to
850 this release, especially Matt Kraai, Larry Doolittle, and Kent Robotti.
851 <p>
852<p> <li> <b>26 September 2000 -- BusyBox 0.47 released</b>
853<br>
854
855 This release fixes lots of bugs (including an ugly bug in 0.46
856 syslogd that could fork-bomb your system). Added several new
857 apps: rdate, wget, getopt, dos2unix, unix2dos, reset, unrpm,
858 renice, xargs, and expr. syslogd now supports network logging.
859 There are the usual tar updates. Most apps now use getopt for
860 more correct option parsing.
861 See the <a href="downloads/Changelog">changelog</a>
862 for complete details.
863
864
865<p> <li> <b>11 July 2000 -- BusyBox 0.46 released</b>
866<br>
867
868 This release fixes several bugs (including a ugly bug in tar,
869 and fixes for NFSv3 mount support). Added a dumpkmap to allow
870 people to dump a binary keymaps for use with 'loadkmap', and a
871 completely reworked 'grep' and 'sed' which should behave better.
872 BusyBox shell can now also be used as a login shell.
873 See the <a href="downloads/Changelog">changelog</a>
874 for complete details.
875
876
877<p> <li> <b>21 June 2000 -- BusyBox 0.45 released</b>
878<br>
879
880 This release has been slow in coming, but is very solid at this
881 point. BusyBox now supports libc5 as well as GNU libc. This
882 release provides the following new apps: cut, tr, insmod, ar,
883 mktemp, setkeycodes, md5sum, uuencode, uudecode, which, and
884 telnet. There are bug fixes for just about every app as well (see
885 the <a href="downloads/Changelog">changelog</a> for
886 details).
887 <p>
888 Also, some exciting infrastructure news! Busybox now has its own
889 <a href="lists/busybox/">mailing list</a>,
890 publically browsable
891 <a href="/cgi-bin/cvsweb/busybox/">CVS tree</a>,
892 anonymous
893 <a href="cvs_anon.html">CVS access</a>, and
894 for those that are actively contributing there is even
895 <a href="cvs_write.html">CVS write access</a>.
896 I think this will be a huge help to the ongoing development of BusyBox.
897 <p>
898 Also, for the curious, there is no 0.44 release. Somehow 0.44 got announced
899 a few weeks ago prior to its actually being released. To avoid any confusion
900 we are just skipping 0.44.
901 <p>
902 Many thanks go out to the many people that have contributed to this release
903 of BusyBox (esp. Pavel Roskin)!
904
905
906<p> <li> <b>19 April 2000 -- syslogd bugfix</b>
907<br>
908Turns out that there was still a bug in busybox syslogd.
909For example, with the following test app:
910<pre>
911#include &lt;syslog.h&gt;
912
913int do_log(char* msg, int delay)
914{
915 openlog("testlog", LOG_PID, LOG_DAEMON);
916 while(1) {
917 syslog(LOG_ERR, "%s: testing one, two, three\n", msg);
918 sleep(delay);
919 }
920 closelog();
921 return(0);
922};
923
924int main(void)
925{
926 if (fork()==0)
927 do_log("A", 2);
928 do_log("B", 3);
929}
930</pre>
931it should be logging stuff from both "A" and "B". As released in 0.43 only stuff
932from "A" would have been logged. This means that if init tries to log something
933while say ppp has the syslog open, init would block (which is bad, bad, bad).
934<p>
935Karl M. Hegbloom has created a fix for the problem.
936Thanks Karl!
937
938
939<p> <li> <b>18 April 2000 -- BusyBox 0.43 released (finally!)</b>
940<br>
941I have finally gotten everything into a state where I feel pretty
942good about things. This is definitely the most stable, solid release
943so far. A lot of bugs have been fixed, and the following new apps
944have been added: sh, basename, dirname, killall, uptime,
945freeramdisk, tr, echo, test, and usleep. Tar has been completely
946rewritten from scratch. Bss size has also been greatly reduced.
947More details are available in the
948<a href="downloads/Changelog">changelog</a>.
949Oh, and as a special bonus, I wrote some fairly comprehensive
950<em>documentation</em>, complete with examples and full usage information.
951
952<p>
953Many thanks go out to the fine people that have helped by submitting patches
954and bug reports; particularly instrumental in helping for this release were
955Karl Hegbloom, Pavel Roskin, Friedrich Vedder, Emanuele Caratti,
956Bob Tinsley, Nicolas Pitre, Avery Pennarun, Arne Bernin, John Beppu, and Jim Gleason.
957There were others so if I somehow forgot to mention you, I'm very sorry.
958<p>
959
960You can grab BusyBox 0.43 tarballs <a href="downloads">here</a>.
961
962<p> <li> <b>9 April 2000 -- BusyBox 0.43 pre release</b>
963<br>
964Unfortunately, I have not yet finished all the things I want to
965do for BusyBox 0.43, so I am posting this pre-release for people
966to poke at. This contains my complete rewrite of tar, which now weighs in at
9675k (7k with all options turned on) and works for reading and writing
968tarballs (which it does correctly for everything I have been able to throw
969at it). Tar also (optionally) supports the "--exclude" option (mainly because
970the Linux Router Project folks asked for it). This also has a pre-release
971of the micro shell I have been writing. This pre-release should be stable
972enough for production use -- it just isn't a release since I have some structural
973changes I still want to make.
974<p>
975The pre-release can be found <a href="downloads">here</a>.
976Please let me know ASAP if you find <em>any</em> bugs.
977
978<p> <li> <b>28 March 2000 -- Andersen Baby Boy release</b>
979<br>
980I am pleased to announce that on Tuesday March 28th at 5:48pm, weighing in at 7
981lbs. 12 oz, Micah Erik Andersen was born at LDS Hospital here in Salt Lake City.
982He was born in the emergency room less then 5 minutes after we arrived -- and
983it was such a relief that we even made it to the hospital at all. Despite the
984fact that I was driving at an amazingly unlawful speed and honking at everybody
985and thinking decidedly unkind thoughts about the people in our way, my wife
986(inconsiderate of my feelings and complete lack of medical training) was lying
987down in the back seat saying things like "I think I need to start pushing now"
988(which she then proceeded to do despite my best encouraging statements to the
989contrary).
990<p>
991Anyway, I'm glad to note that despite the much-faster-than-we-were-expecting
992labor, both Shaunalei and our new baby boy are doing wonderfully.
993<p>
994So now that I am done with my excuse for the slow release cycle...
995Progress on the next release of BusyBox has been slow but steady. I expect
996to have a release sometime during the first week of April. This release will
997include a number of important changes, including the addition of a shell, a
998re-write of tar (to accommodate the Linux Router Project), and syslogd can now
999accept multiple concurrent connections, fixing lots of unexpected blocking
1000problems.
1001
1002
1003<p> <li> <b>11 February 2000 -- BusyBox 0.42 released</b>
1004<br>
1005
1006 This is the most solid BusyBox release so far. Many, many
1007 bugs have been fixed. See the
1008 <a href="downloads/Changelog">changelog</a> for details.
1009
1010 Of particular interest, init will now cleanly unmount
1011 filesystems on reboot, cp and mv have been rewritten and
1012 behave much better, and mount and umount no longer leak
1013 loop devices. Many thanks go out to Randolph Chung,
1014 Karl M. Hegbloom, Taketoshi Sano, and Pavel Roskin for
1015 their hard work on this release of BusyBox. Please pound
1016 on it and let me know if you find any bugs.
1017
1018<p> <li> <b>19 January 2000 -- BusyBox 0.41 released</b>
1019<br>
1020
1021 This release includes bugfixes to cp, mv, logger, true, false,
1022 mkdir, syslogd, and init. New apps include wc, hostid,
1023 logname, tty, whoami, and yes. New features include loop device
1024 support in mount and umount, and better TERM handling by init.
1025 The changelog can be found <a href="downloads/Changelog">here</a>.
1026
1027<p> <li> <b>7 January 2000 -- BusyBox 0.40 released</b>
1028<br>
1029
1030 This release includes bugfixes to init (now includes inittab support),
1031 syslogd, head, logger, du, grep, cp, mv, sed, dmesg, ls, kill, gunzip, and mknod.
1032 New apps include sort, uniq, lsmod, rmmod, fbset, and loadacm.
1033 In particular, this release fixes an important bug in tar which
1034 in some cases produced serious security problems.
1035 As always, the changelog can be found <a href="downloads/Changelog">here</a>.
1036
1037<p> <li> <b>11 December 1999 -- BusyBox Website</b>
1038<br>
1039 I have received permission from Bruce Perens (the original author of BusyBox)
1040 to set up this site as the new primary website for BusyBox. This website
1041 will always contain pointers to the latest and greatest, and will also
1042 contain the latest documentation on how to use BusyBox, what it can do,
1043 what arguments its apps support, etc.
1044
1045<p> <li> <b>10 December 1999 -- BusyBox 0.39 released</b>
1046<br>
1047 This release includes fixes to init, reboot, halt, kill, and ls, and contains
1048 the new apps ping, hostname, mkfifo, free, tail, du, tee, and head. A full
1049 changelog can be found <a href="downloads/Changelog">here</a>.
1050<p> <li> <b>5 December 1999 -- BusyBox 0.38 released</b>
1051<br>
1052 This release includes fixes to tar, cat, ls, dd, rm, umount, find, df,
1053 and make install, and includes new apps syslogd/klogd and logger.
1054
1055
1056</ul>
1057
1058
1059<!--#include file="footer.html" -->
1060
diff --git a/busybox/docs/busybox.net/products.html b/busybox/docs/busybox.net/products.html
deleted file mode 100644
index 6ca0e3c92..000000000
--- a/busybox/docs/busybox.net/products.html
+++ /dev/null
@@ -1,166 +0,0 @@
1<!--#include file="header.html" -->
2
3
4<h3>Products/Projects Using BusyBox</h3>
5
6Do you use BusyBox? I'd love to know about it and
7I'd be happy to link to you.
8
9<p>
10I know of the following products and/or projects that use BusyBox --
11listed in the order I happen to add them to the web page:
12
13<ul>
14
15
16<li><a href="/cgi-bin/cvsweb/buildroot/">buildroot</a><br>A configurable
17means for building your own busybox/uClibc based system systems.
18
19<li><a href="http://www.pengutronix.de/software/ptxdist_en.html">PTXdist</a><br>another
20configurable means for building your own busybox based system systems.
21
22</li><li><a href=
23"http://cvs.debian.org/boot-floppies/">
24Debian installer (boot floppies) project</a>
25
26</li><li><a href="http://redhat.com/">Red Hat installer</a>
27
28</li><li><a href=
29"http://distro.ibiblio.org/pub/Linux/distributions/slackware/slackware-current/source/rootdisks/">
30Slackware Installer</a>
31
32</li><li><a href="http://www.gentoo.org/">Gentoo Linux install/boot CDs</a>
33</li><li><a href="http://www.mandrake.com/">The Mandrake installer</a>
34
35</li><li><a href="http://Leaf.SourceForge.net">Linux Embedded Appliance Firewall</a><br>The sucessor of the Linux Router Project, supporting all sorts of embedded Linux gateways, routers, wireless routers, and firewalls.
36
37</li><li><a href=
38"http://www.toms.net/rb/">tomsrtbt</a>
39
40</li><li><a href="http://www.stormix.com/">Stormix
41Installer</a>
42
43</li><li><a href=
44"http://www.emacinc.com/linux2_sbc.htm">EMAC Linux
452.0 SBC</a>
46
47</li><li><a href="http://www.trinux.org/">Trinux</a>
48
49</li><li><a href="http://oddas.sourceforge.net/">ODDAS
50project</a>
51
52</li><li><a href="http://byld.sourceforge.net/">Build Your
53Linux Disk</a>
54
55</li><li><a href=
56"http://ibiblio.org/pub/Linux/system/recovery">Zdisk</a>
57
58</li><li><a href="http://www.adtran.com">AdTran -
59VPN/firewall VPN Linux Distribution</a>
60
61</li><li><a href="http://mkcdrec.ota.be/">mkCDrec - make
62CD-ROM recovery</a>
63
64</li><li><a href=
65"http://recycle.lbl.gov/~ldoolitt/bse/">Linux on
66nanoEngine</a>
67
68</li><li><a href=
69"http://www.zelow.no/floppyfw/">Floppyfw</a>
70
71</li><li><a href="http://www.ltsp.org/">Linux Terminal
72Server Project</a>
73
74</li><li><a href="http://www.devil-linux.org/">Devil-Linux</a>
75
76</li><li><a href="http://dutnux.sourceforge.net/">DutNux</a>
77
78</li><li><a href="http://www.microwerks.net/~hugo/mindi/">Mindi</a>
79
80</li><li><a href="http://www.minimalinux.org/ttylinux/">ttylinux</a>
81
82</li><li><a href="http://www.coyotelinux.com/">Coyote Linux</a>
83
84</li><li><a href="http://www.partimage.org/">Partition
85Image</a>
86
87</li><li><a href="http://www.fli4l.de/">fli4l the on(e)-disk-router</a>
88
89</li><li><a href="http://tinfoilhat.cultists.net/">Tinfoil
90Hat Linux</a>
91
92</li><li><a href="http://sourceforge.net/projects/gp32linux/">gp32linux</a>
93</li><li><a href="http://familiar.handhelds.org/">Familiar Linux</a><br>A linux distribution for handheld computers
94</li><li><a href="http://rescuecd.sourceforge.net/">Timo's Rescue CD Set</a>
95</li><li><a href="http://sf.net/projects/netstation/">Netstation</a>
96</li><li><a href="http://www.fiwix.org/">GNU/Fiwix Operating System</a>
97</li><li><a href="http://www.softcraft.com/">Generations Linux</a>
98</li><li><a href="http://systemimager.org/relatedprojects/">SystemImager / System Installation Suite</a>
99</li><li><a href="http://www.bablokb.de/gendist/">GENDIST distribution generator</a>
100</li><li><a href="http://diet-pc.sourceforge.net/">DIET-PC embedded Linux thin client distribution</a>
101</li><li><a href="http://byzgl.sourceforge.net/">BYZantine Gnu/Linux</a>
102</li><li><a href="http://dban.sourceforge.net/">Darik's Boot and Nuke</a>
103</li><li><a href="http://www.timesys.com/">TimeSys real-time Linux</a>
104</li><li><a href="http://movix.sf.net/">MoviX</a><br>Boots from CD and automatically plays every video file on the CD
105</li><li><a href="http://katamaran.sourceforge.net">katamaran</a><br>Linux, X11, xfce windowmanager, based on BusyBox
106</li><li><a href="http://www.sourceforge.net/projects/simplygnustep">Prometheus SimplyGNUstep</a>
107</li><li><a href="http://www.renyi.hu/~ekho/lowlife/">lowlife</a><br>A documentation project on how to make your own uClibc-based systems and floppy.
108</li><li><a href="http://metadistros.hispalinux.es/">Metadistros</a><br>a project to allow you easily make Live-CD distributions.
109</li><li><a href="http://salvare.sourceforge.net/">Salvare</a><br>More Linux than tomsrtbt but less than Knoppix, aims to provide a useful workstation as well as a rescue disk.
110</li><li><a href="http://www.stresslinux.org/">stresslinux</a><br>minimal linux distribution running from a bootable cdrom or via PXE.
111</li><li><a href="http://thinstation.sourceforge.net/">thinstation</a><br>convert standard PCs into full-featured diskless thinclients.
112</li><li><a href="http://www.uhulinux.hu/">UHU-Linux Hungary</a>
113</li><li><a href="http://deep-water.berlios.de/">Deep-Water Linux</a>
114</li><li><a href="http://www.freesco.org/">Freesco router</a>
115</li><li><a href="http://Sentry.SourceForge.net/">Sentry Firewall CD</a>
116
117
118
119</li><li><a href="http://tuxscreen.net">Tuxscreen Linux Phone</a>
120</li><li><a href="http://www.kerbango.com/">The Kerbango Internet Radio</a>
121</li><li><a href="http://www.linuxmagic.com/vpn/">LinuxMagic VPN Firewall</a>
122</li><li><a href="http://www.isilver-inc.com/">I-Silver Linux appliance servers</a>
123</li><li><a href="http://zaurus.sourceforge.net/">Sharp Zaurus PDA</a>
124</li><li><a href="http://www.cyclades.com/">Cyclades-TS and other Cyclades products</a>
125</li><li><a href="http://www.linksys.com/products/product.asp?prid=508">Linksys WRT54G - Wireless-G Broadband Router</a>
126</li><li><a href="http://www.dell.com/us/en/biz/topics/sbtopic_005_truemobile.htm">Dell TrueMobile 1184</a>
127</li><li><a href="http://actiontec.com/products/modems/dual_pcmodem/dpm_overview.html">Actiontec Dual PC Modem</a>
128</li><li><a href="http://www.kiss-technology.com/">Kiss DP Series DVD players</a>
129</li><li><a href="http://www.netgear.com/products/prod_details.asp?prodID=170">NetGear WG602 wireless router</a>
130 <br>with sources <a href="http://www.netgear.com/support/support_details.asp?dnldID=453">here</a>
131</li><li><a href="http://www.trendware.com/products/TEW-411BRP.htm">TRENDnet TEW-411BRP 802.11g Wireless AP/Router/Switch</a>
132 <br>Source for busybox and udhcp <a href="http://www.trendware.com/asp/download/fileinfo.asp?file_id=277&B1=Search">here</a> though no kernel source is provided.
133</li><li><a href="http://www.buffalo-technology.com/webcontent/products/wireless/wbr-g54.htm">Buffalo WBR-G54 wireless router</a>
134 </li><li><a href="http://www.asus.com/products/communication/wireless/wl-300g/overview.htm">ASUS WL-300g Wireless LAN Access Point</a>
135 <br>with source<a href="http://www.asus.com.tw/support/download/item.aspx?ModelName=WL-300G">here</a>
136 </li><li><a href="http://catalog.belkin.com/IWCatProductPage.process?Merchant_Id=&Section_Id=201522&pcount=&Product_Id=136493">Belkin 54g Wireless DSL/Cable Gateway Router</a>
137 <br>with source<a href="http://web.belkin.com/support/gpl.asp">here</a>
138 <li><a href="http://www.acronis.com/products/partitionexpert/">Acronis PartitionExpert 2003</a>
139 <br>includes a heavily modified BusyBox v0.60.5 with built in
140 cardmgr, device detection, gpm, lspci, etc. Also includes udhcp,
141 uClibc 0.9.26, a heavily patched up linux kernel, etc. Source
142 can only be obtained <a href="http://www.acronis.com/files/gpl/linux.tar.bz2">here</a>
143
144</li><li><a href="http://www.usr.com/">U.S. Robotics Sureconnect 4-port ADSL router</a><br>
145 with source <a href="http://www.usr.com/support/s-gpl-code.asp">here</a>
146</li><li><a href="http://www.actiontec.com/products/broadband/54mbps_wireless_gateway_1p/index.html">
147 ActionTec GT701-WG Wireless Gateway/DSL Modem</a>
148 with source <a href="http://128.121.226.214/gtproducts/index.html">here</a>
149</li><li><a href="http://smartlinux.sourceforge.net/">S.M.A.R.T. Linux</a>
150</li><li><a href="http://www.dlink.com/">DLink - Model GSL-G604T, DSL-300T, and possibly other models</a>
151 with source <a href="ftp://ftp.dlink.co.uk/dsl_routers_modems/">here,</a>
152 with source <a href="ftp://ftp.dlink.de/dsl-products/">and here,</a>
153 and quite possibly other places as well. You may need to dig down a bit
154 to find the source, but it does seem to be there.
155</li><li><a href="http://www.siemens-mobile.de/cds/frontdoor/0,2241,de_de_0_42931_rArNrNrNrN,00.html">Siemens SE515 DSL router</a>
156 with source <a href="http://now-portal.c-lab.de/projects/gigaset/">here, I think...</a>
157 with some details <a href="http://heinz.hippenstiel.org/familie/hp/hobby/gigaset_se515dsl.html">here.</a>
158</li><li><a href="http://frwt.stim.ru/">Free Remote Windows Terminal</a>
159
160
161</li>
162</ul>
163
164
165<!--#include file="footer.html" -->
166
diff --git a/busybox/docs/busybox.net/screenshot.html b/busybox/docs/busybox.net/screenshot.html
deleted file mode 100644
index 9c05791db..000000000
--- a/busybox/docs/busybox.net/screenshot.html
+++ /dev/null
@@ -1,57 +0,0 @@
1<!--#include file="header.html" -->
2
3
4<!-- Begin Screenshot -->
5
6<h3> Busybox Screenshot! </h3>
7
8
9Everybody loves to look at screenshots, so here is a live action screenshot of BusyBox.
10
11<pre style="background-color: black; color: lightgreen; padding: 5px;
12font-family: monospace; font-size: smaller;" width="100">
13
14
15$ ./busybox
16BusyBox v1.00 (2004.10.13-04:49+0000) multi-call binary
17
18Usage: busybox [function] [arguments]...
19 or: [function] [arguments]...
20
21 BusyBox is a multi-call binary that combines many common Unix
22 utilities into a single executable. Most people will create a
23 link to busybox for each function they wish to use, and BusyBox
24 will act like whatever it was invoked as.
25
26Currently defined functions:
27
28 [, addgroup, adduser, adjtimex, ar, arping, ash, awk, basename, bunzip2,
29 busybox, bzcat, cal, cat, chgrp, chmod, chown, chroot, chvt, clear, cmp,
30 cp, cpio, crond, crontab, cut, date, dc, dd, deallocvt, delgroup, deluser,
31 devfsd, df, dirname, dmesg, dos2unix, dpkg, dpkg-deb, du, dumpkmap,
32 dumpleases, echo, egrep, env, expr, false, fbset, fdflush, fdformat, fdisk,
33 fgrep, find, fold, free, freeramdisk, fsck.minix, ftpget, ftpput, getopt,
34 getty, grep, gunzip, gzip, halt, hdparm, head, hexdump, hostid, hostname,
35 httpd, hush, hwclock, id, ifconfig, ifdown, ifup, inetd, init, insmod,
36 install, ip, ipaddr, ipcalc, iplink, iproute, iptunnel, kill, killall,
37 klogd, lash, last, length, linuxrc, ln, loadfont, loadkmap, logger, login,
38 logname, logread, losetup, ls, lsmod, makedevs, md5sum, mesg, mkdir,
39 mkfifo, mkfs.minix, mknod, mkswap, mktemp, modprobe, more, mount, msh, mt,
40 mv, nameif, nc, netstat, nslookup, od, openvt, passwd, patch, pidof, ping,
41 ping6, pipe_progress, pivot_root, poweroff, printf, ps, pwd, rdate,
42 readlink, realpath, reboot, renice, reset, rm, rmdir, rmmod, route, rpm,
43 rpm2cpio, run-parts, rx, sed, seq, setkeycodes, sha1sum, sleep, sort,
44 start-stop-daemon, strings, stty, su, sulogin, swapoff, swapon, sync,
45 sysctl, syslogd, tail, tar, tee, telnet, telnetd, test, tftp, time, top,
46 touch, tr, traceroute, true, tty, udhcpc, udhcpd, umount, uname,
47 uncompress, uniq, unix2dos, unzip, uptime, usleep, uudecode, uuencode,
48 vconfig, vi, vlock, watch, watchdog, wc, wget, which, who, whoami, xargs,
49 yes, zcat
50
51
52$ <blink>_</blink>
53
54</pre>
55
56<!--#include file="footer.html" -->
57
diff --git a/busybox/docs/busybox.net/shame.html b/busybox/docs/busybox.net/shame.html
deleted file mode 100644
index 99807c17a..000000000
--- a/busybox/docs/busybox.net/shame.html
+++ /dev/null
@@ -1,77 +0,0 @@
1<!--#include file="header.html" -->
2
3
4<h3>Hall of Shame!!!</h3>
5
6The following products and/or projects appear to use BusyBox, but do not
7appear to release source code as required by the <a
8href="/license.html">BusyBox license</a>. This is a violation of the law!
9The distributors of these products are invited to contact <a href=
10"mailto:andersen@codepoet.org">Erik Andersen</a> if they have any confusion
11as to what is needed to bring their products into compliance, or if they have
12already brought their product into compliance and wish to be removed from the
13Hall of Shame.
14
15<p>
16
17Here are the details of <a href="/license.html">exactly how to comply
18with the BusyBox license</a>, so there should be no question as to
19exactly what is expected.
20Complying with the Busybox license is easy and completely free, so the
21companies listed below should be ashamed of themselves. Furthermore, each
22product listed here is subject to being legally ordered to cease and desist
23distribution for violation of copyright law, and the distributor of each
24product is subject to being sued for statutory copyright infringement damages
25of up to $150,000 per work plus legal fees. Nobody wants to be sued, and <a
26href="mailto:andersen@codepoet.org">Erik</a> certainly would prefer to spend
27his time doing better things than sue people. But he will sue if forced to
28do so to maintain compliance.
29
30<p>
31
32Do everyone a favor and don't break the law -- if you use busybox, comply with
33the busybox license by releasing the source code with your product.
34
35<p>
36
37<ul>
38
39 <li><a href="http://www.trittontechnologies.com/products.html">Tritton Technologies NAS120</a>
40 <br>see <a href="http://www.ussg.iu.edu/hypermail/linux/kernel/0404.0/1611.html">here for details</a>
41 <li><a href="http://www.macsense.com/product/homepod/">Macsense HomePod</a>
42 <br>with details
43 <a href="http://developer.gloolabs.com/modules.php?op=modload&name=Forums&file=viewtopic&topic=123&forum=7">here</a>
44 <li><a href="http://www.cpx.com/products.asp?c=Wireless+Products">Compex Wireless Products</a>
45 <br>appears to be running v0.60.5 with Linux version 2.4.20-uc0 on ColdFire,
46 but no source code is mentioned or offered.
47 <li><a href="http://www.inventel.com/en/product/datasheet/10/">Inventel DW 200 wireless/ADSL router</a>
48 <li><a href="http://www.sweex.com/product.asp">Sweex DSL router</a>
49 <br>appears to be running BusyBox v1.00-pre2 and udhcpd, but no source
50 code is mentioned or offered.
51 <li><a href="http://www.trendware.com/products/TEW-410APB.htm">TRENDnet TEW-410APB</a>
52 </li><li><a href="http://www.hauppauge.com/Pages/products/data_mediamvp.html">Hauppauge Media MVP</a>
53 <br>Hauppauge contacted me on 16 Dec 2003, and claims to be working on resolving this problem.
54 </li><li><a href="http://www.hitex.com/download/adescom/data/">TriCore</a>
55 </li><li><a href="http://www.allnet.de/">ALLNET 0186 wireless router</a>
56 </li><li><a href="http://www.dmmtv.com/">Dreambox DM7000S DVB Satellite Receiver</a>
57 <br> Dream Multimedia contacted me on 22 Dec 2003 and is working on resolving this problem.
58 <br> Source _may_ be here: http://cvs.tuxbox.org/cgi-bin/viewcvs.cgi/tuxbox/cdk/
59 </li><li><a href="http://testing.lkml.org/slashdot.php?mid=331690">Sigma Designs EM8500 based DVD players</a>
60 <br>Source for the Sigma Designs reference platform is found here<br>
61 <a href="http://www.uclinux.org/pub/uClinux/ports/arm/EM8500/uClinux-2.4-sigma.tar.gz">uClinux-2.4-sigma.tar.gz</a>, so while Sigma Designs itself appears to be in compliance, as far as I can tell,
62 no vendors of Sigma Designs EM8500 based devices actually comply with the GPL....
63 </li><li><a href="http://testing.lkml.org/slashdot.php?mid=433790">Liteon LVD2001 DVD player using the Sigma Designs EM8500</a>
64 </li><li><a href="http://www.rimax.net/">Rimax DVD players using the Sigma Designs EM8500</a>
65 </li><li><a href="http://www.vinc.us/">Bravo DVD players using the Sigma Designs EM8500</a>
66 </li><li><a href="http://www.hb-direct.com/">H&B DX3110 Divx player based on Sigma Designs EM8500</a>
67 </li><li><a href="http://www.recospa.it/mdpro1/index.php">United *DVX4066 mpeg4 capable DVD players</a>
68 </li><li><a href="http://www.a-link.com/RR64AP.html">Avaks alink Roadrunner 64</a>
69 <br> Partial source available, based on source distributed under NDA from <a href="http://www.lsilogic.com/products/dsl_platform_solutions/hb_linuxr2_2.html"> LSILogic</a>. Why the NDA LSILogic, what are you hiding ?
70 <br>To verify the Avaks infrigment see my slashdot <a href="http://slashdot.org/~bug1/journal/">journal</a>.
71 </li><li>Undoubtedly there are others... Please report them so we can shame them (or if necessary sue them) into compliance.
72
73</ul>
74
75
76<!--#include file="footer.html" -->
77
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-03-22 19:40:07 +0000