summaryrefslogtreecommitdiff
path: root/docs/busybox.net
diff options
context:
space:
mode:
authorEric Andersen <andersen@codepoet.org>2004-10-13 09:42:10 +0000
committerEric Andersen <andersen@codepoet.org>2004-10-13 09:42:10 +0000
commit9395ca4f6832a806737eca247f2758468f0cecd1 (patch)
treeed8fde959895391dfa6d376bfda9beb512fb9f42 /docs/busybox.net
parent9789bf1019e27b3b73d045515bf59c734f964066 (diff)
downloadbusybox-w32-1_00.tar.gz
busybox-w32-1_00.tar.bz2
busybox-w32-1_00.zip
prepare for release1_00
Diffstat (limited to 'docs/busybox.net')
-rw-r--r--docs/busybox.net/FAQ.html28
-rw-r--r--docs/busybox.net/license.html67
-rw-r--r--docs/busybox.net/news.html142
-rw-r--r--docs/busybox.net/oldnews.html136
-rw-r--r--docs/busybox.net/products.html24
-rw-r--r--docs/busybox.net/screenshot.html2
-rw-r--r--docs/busybox.net/shame.html11
7 files changed, 252 insertions, 158 deletions
diff --git a/docs/busybox.net/FAQ.html b/docs/busybox.net/FAQ.html
index 294e219a7..a9324ae26 100644
--- a/docs/busybox.net/FAQ.html
+++ b/docs/busybox.net/FAQ.html
@@ -18,6 +18,7 @@ have additions to this FAQ document, we would love to add them,
18<li><a href="#demanding">I demand that you to add &lt;favorite feature&gt; right now! How come 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 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> 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>
21<li><a href="#helpme">I need help with BusyBox! What should I do?</a> 22<li><a href="#helpme">I need help with BusyBox! What should I do?</a>
22<li><a href="#contracts">I need you to add &lt;favorite feature&gt;! Are the BusyBox developers willing to 23<li><a href="#contracts">I need you to add &lt;favorite feature&gt;! Are the BusyBox developers willing to
23 be paid in order to fix bugs or add in &lt;favorite feature&gt;? Are you willing to provide 24 be paid in order to fix bugs or add in &lt;favorite feature&gt;? Are you willing to provide
@@ -146,6 +147,27 @@ have additions to this FAQ document, we would love to add them,
146 147
147<hr /> 148<hr />
148<p> 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>
149<h2><a name="demanding">I demand that you to add &lt;favorite feature&gt; right now! How come 171<h2><a name="demanding">I demand that you to add &lt;favorite feature&gt; right now! How come
150 you don't answer all my questions on the mailing list instantly? I demand 172 you don't answer all my questions on the mailing list instantly? I demand
151 that you help me with all of my problems <em>Right Now</em>!</a></h2> 173 that you help me with all of my problems <em>Right Now</em>!</a></h2>
@@ -198,8 +220,8 @@ have additions to this FAQ document, we would love to add them,
198 href="http://codepoet-consulting.com/">CodePoet Consulting</a> to bid 220 href="http://codepoet-consulting.com/">CodePoet Consulting</a> to bid
199 on your project. If Erik is too busy to personally add your feature, there 221 on your project. If Erik is too busy to personally add your feature, there
200 are many other active BusyBox contributors who will almost certainly be able 222 are many other active BusyBox contributors who will almost certainly be able
201 to help you out. Erik can contact them and ask them about their availability, 223 to help you out. Erik can contact them privatly, and may even let you to
202 and may even ask you to post your request for services on the mailing list. 224 post your request for services on the mailing list.
203 225
204 226
205<hr /> 227<hr />
@@ -218,7 +240,7 @@ have additions to this FAQ document, we would love to add them,
218 <input type="hidden" name="cmd" value="_xclick"> 240 <input type="hidden" name="cmd" value="_xclick">
219 <input type="hidden" name="business" value="andersen@codepoet.org"> 241 <input type="hidden" name="business" value="andersen@codepoet.org">
220 <input type="hidden" name="item_name" value="Support BusyBox"> 242 <input type="hidden" name="item_name" value="Support BusyBox">
221 <input type="hidden" name="image_url" value="https://codepoet-consulting.com/images/codepoet.png"> 243 <input type="hidden" name="image_url" value="http://codepoet-consulting.com/images/codepoet.png">
222 <input type="hidden" name="no_shipping" value="1"> 244 <input type="hidden" name="no_shipping" value="1">
223 <input type="image" src="images/donate.png" name="submit" alt="Make donation using PayPal"> 245 <input type="image" src="images/donate.png" name="submit" alt="Make donation using PayPal">
224 </form> 246 </form>
diff --git a/docs/busybox.net/license.html b/docs/busybox.net/license.html
index 0e27c3956..14324f1df 100644
--- a/docs/busybox.net/license.html
+++ b/docs/busybox.net/license.html
@@ -10,12 +10,32 @@ whatsoever, this page attempts to summarize what you should do to
10ensure you do not accidentally violate the law. 10ensure you do not accidentally violate the law.
11 11
12<p> 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.
13 25
14<p> 26<p>
15 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
16BusyBox is licensed under the GNU General Public License , which 34BusyBox is licensed under the GNU General Public License , which
17is generally just abbreviated simply as the GPL license, or 35is generally just abbreviated as the GPL license, or
18just the GPL. <a href="/products.html">Anyone thinking of shipping 36just the GPL.
37<p>
38<a href="/products.html">Anyone thinking of shipping
19BusyBox as part of a product</a> should be familiar with the 39BusyBox as part of a product</a> should be familiar with the
20licensing terms under which they are allowed to use and 40licensing terms under which they are allowed to use and
21distribute BusyBox. You are advised to take a look over the 41distribute BusyBox. You are advised to take a look over the
@@ -53,37 +73,39 @@ applications such as BusyBox is mandatory.
53 73
54<p> 74<p>
55 75
56<b>Accompanied by source</b> generally means you place the full 76<b>Accompanied by source</b> generally means you distribute the full
57source code for all GPL'd products such as BusyBox on a driver CD 77source code for all GPL'd products including BusyBox along with your
58somewhere. Full source code includes the BusyBox ".config" file 78product, such as by placing it somewhere on a driver CD. Full source
59used when your shipping BusyBox binary was compiled. 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.
60 82
61<p> 83<p>
62 84
63<b>A written offer</b> generally means that somewhere in the 85<b>A written offer</b> generally means that somewhere in the
64docs for your product, you write something like 86documentation for your product, you write something like
65 87
66<blockquote> 88<blockquote>
67The GPL source code contained in this product is available as a 89The GPL source code contained in this product is available as a
68free download from http://blah.blah.blah/ 90free download from http://blah.blah.blah/
69</blockquote> 91</blockquote>
70Or you can offer source by writing 92Alternatively, you can offer the source code by writing
71somewhere in the docs for your product something like 93somewhere in the documentation for your product something like
72<blockquote> 94<blockquote>
73If you would like a copy of the GPL source code in this product 95If you would like a copy of the GPL source code contained in this
74on a CD, please send $9.99 to &lt;address&gt; for the costs of 96product shipped to you on CD, please send $9.99 to &lt;address&gt;
75preparing and mailing a CD to you. 97which covers the cost of preparing and mailing a CD to you.
76</blockquote> 98</blockquote>
77<p> 99<p>
78 100
79Keep in mind though that if you distribute GPL'd binaries online 101Keep in mind though that if you distribute GPL'd binaries online (as is often
80(as is often done when supplying firmware updates), it is highly 102done when supplying firmware updates), it is <b>highly</b> recommended that you
81recommended that you make the corresponding source available online 103make the corresponding source available online at the same place. Regardless,
82at the same place. Regardless, you <b>must</b> either make source 104if you distribute a binary copy of BusyBox online (such as part of a firmware
83available online (i.e. <b>accompanied by source</b>) and/or inform 105update) you <b>must</b> either make source available online (i.e.
84those downloading firmware updates of their right to obtain source 106<b>accompanied by source</b>) and/or inform those downloading firmware updates
85(i.e. <b>a written offer</b>). Failure to do so is a violation of 107of their right to obtain source (i.e. <b>a written offer</b>). Failure to do
86your licensing obligations. 108so is a violation of your licensing obligations.
87 109
88 110
89<p> 111<p>
@@ -97,6 +119,7 @@ If you distribute any GPL'd binaries, you must also make source available
97as discussed on this webpage. 119as discussed on this webpage.
98 120
99<p> 121<p>
122<h3>A Good Example</h3>
100 123
101These days, <a href="http://www.linksys.com/">Linksys</a> is 124These days, <a href="http://www.linksys.com/">Linksys</a> is
102doing a good job at complying with the GPL, they get to be an 125doing a good job at complying with the GPL, they get to be an
@@ -104,8 +127,8 @@ example of how to do things right. Please take a moment and
104check out what they do with 127check out what they do with
105<a href="http://www.linksys.com/download/firmware.asp?fwid=178"> 128<a href="http://www.linksys.com/download/firmware.asp?fwid=178">
106distributing the firmware for their WRT54G Router.</a> 129distributing the firmware for their WRT54G Router.</a>
107Following their example would be a fine way to ensure you have 130Following their example would be a fine way to ensure that you
108fulfilled your licensing obligations. 131have also fulfilled your licensing obligations.
109 132
110 133
111<!--#include file="footer.html" --> 134<!--#include file="footer.html" -->
diff --git a/docs/busybox.net/news.html b/docs/busybox.net/news.html
index 1f5ebc34b..0d4c81bab 100644
--- a/docs/busybox.net/news.html
+++ b/docs/busybox.net/news.html
@@ -3,141 +3,43 @@
3 3
4<ul> 4<ul>
5 5
6 <li><b>16 August 2004 -- BusyBox 1.0.0-rc3 released</b><p> 6 <li><b>13 October 2004 -- BusyBox 1.00 released</b><p>
7 7
8 Here goes release candidate 3... 8 When you take a careful look at nearly every embedded Linux device or
9 <p> 9 software distribution shipping today, you will find a copy of BusyBox.
10 The <a href="downloads/Changelog">changelog</a> has all the details. 10 With countless routers, set top boxes, wireless access points, PDAs, and
11 And as usual you can <a href="downloads">download busybox here</a>. 11 who knows what else, the future for Linux and BusyBox on embedded devices
12 12 is looking very bright.
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 13
58 <p> 14 <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 15
94 Here goes the final BusyBox pre-release... This is your last chance for 16 It is therefore with great satisfaction that I declare each and every
95 bug fixes. With luck this will be released as BusyBox 1.0.0 later this 17 device already shipping with BusyBox is now officially out of date.
96 week. Please do not bother to send in patches adding cool new features at 18 The highly anticipated release of BusyBox 1.00 has arrived!
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 19
104 <p> 20 <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 21
109 <p> 22 Over three years in development, BusyBox 1.00 represents a tremendous
110 The <a href="downloads/Changelog">changelog</a> has all the details. 23 improvement over the old 0.60.x stable series. Now featuring a Linux
111 And as usual you can <a href="downloads">download busybox here</a>. 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.
112 27
113 <p>Have Fun!
114 <p> 28 <p>
115 29
116 30 If you are already using BusyBox, you are strongly encouraged to upgrade to
117 <p> 31 BusyBox 1.00. If you are considering developing an embedded Linux device
118 <li><b>23 February 2004 -- BusyBox 1.0.0-pre8 released</b><p> 32 or software distribution, you may wish to investigate if using BusyBox is
119 33 right for your application. If you need help getting started using
120 Here goes yet another BusyBox pre-release... Please do not bother to send 34 BusyBox, if you wish to donate to help cover expenses, or if you find a bug
121 in patches supplying new features at this time. Only bug-fix patches will 35 and need help reporting it, you are invited to visit the <a
122 be accepted. If you have a cool new feature you would like to see 36 href="FAQ.html">BusyBox FAQ</a>.
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 37
133 <p> 38 <p>
134 39
135 The <a href="downloads/Changelog">changelog</a> has all the details. 40 As usual you can <a href="downloads">download busybox here</a>.
136 And as usual you can <a href="downloads">download busybox here</a>.
137 41
138 <p>Have Fun! 42 <p>Have Fun!
139 <p>
140
141 43
142 <p> 44 <p>
143 <li><b>Old News</b><p> 45 <li><b>Old News</b><p>
diff --git a/docs/busybox.net/oldnews.html b/docs/busybox.net/oldnews.html
index 788224679..83987ecf8 100644
--- a/docs/busybox.net/oldnews.html
+++ b/docs/busybox.net/oldnews.html
@@ -3,6 +3,142 @@
3 3
4<ul> 4<ul>
5 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
6 <li><b>4 February 2004 -- BusyBox 1.0.0-pre7 released</b><p> 142 <li><b>4 February 2004 -- BusyBox 1.0.0-pre7 released</b><p>
7 143
8 There was a bug in -pre6 that broke argument parsing for a 144 There was a bug in -pre6 that broke argument parsing for a
diff --git a/docs/busybox.net/products.html b/docs/busybox.net/products.html
index 527840655..6ca0e3c92 100644
--- a/docs/busybox.net/products.html
+++ b/docs/busybox.net/products.html
@@ -71,17 +71,13 @@ nanoEngine</a>
71</li><li><a href="http://www.ltsp.org/">Linux Terminal 71</li><li><a href="http://www.ltsp.org/">Linux Terminal
72Server Project</a> 72Server Project</a>
73 73
74</li><li><a href= 74</li><li><a href="http://www.devil-linux.org/">Devil-Linux</a>
75"http://www.devil-linux.org/">Devil-Linux</a>
76 75
77</li><li><a href= 76</li><li><a href="http://dutnux.sourceforge.net/">DutNux</a>
78"http://dutnux.sourceforge.net/">DutNux</a>
79 77
80</li><li><a href= 78</li><li><a href="http://www.microwerks.net/~hugo/mindi/">Mindi</a>
81"http://www.microwerks.net/~hugo/mindi/">Mindi</a>
82 79
83</li><li><a href= 80</li><li><a href="http://www.minimalinux.org/ttylinux/">ttylinux</a>
84"http://www.tzi.de/~pharao90/ttylinux">ttylinux</a>
85 81
86</li><li><a href="http://www.coyotelinux.com/">Coyote Linux</a> 82</li><li><a href="http://www.coyotelinux.com/">Coyote Linux</a>
87 83
@@ -93,6 +89,7 @@ Image</a>
93</li><li><a href="http://tinfoilhat.cultists.net/">Tinfoil 89</li><li><a href="http://tinfoilhat.cultists.net/">Tinfoil
94Hat Linux</a> 90Hat Linux</a>
95 91
92</li><li><a href="http://sourceforge.net/projects/gp32linux/">gp32linux</a>
96</li><li><a href="http://familiar.handhelds.org/">Familiar Linux</a><br>A linux distribution for handheld computers 93</li><li><a href="http://familiar.handhelds.org/">Familiar Linux</a><br>A linux distribution for handheld computers
97</li><li><a href="http://rescuecd.sourceforge.net/">Timo's Rescue CD Set</a> 94</li><li><a href="http://rescuecd.sourceforge.net/">Timo's Rescue CD Set</a>
98</li><li><a href="http://sf.net/projects/netstation/">Netstation</a> 95</li><li><a href="http://sf.net/projects/netstation/">Netstation</a>
@@ -149,6 +146,17 @@ Hat Linux</a>
149</li><li><a href="http://www.actiontec.com/products/broadband/54mbps_wireless_gateway_1p/index.html"> 146</li><li><a href="http://www.actiontec.com/products/broadband/54mbps_wireless_gateway_1p/index.html">
150 ActionTec GT701-WG Wireless Gateway/DSL Modem</a> 147 ActionTec GT701-WG Wireless Gateway/DSL Modem</a>
151 with source <a href="http://128.121.226.214/gtproducts/index.html">here</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
152 160
153</li> 161</li>
154</ul> 162</ul>
diff --git a/docs/busybox.net/screenshot.html b/docs/busybox.net/screenshot.html
index e691a16c9..9c05791db 100644
--- a/docs/busybox.net/screenshot.html
+++ b/docs/busybox.net/screenshot.html
@@ -13,7 +13,7 @@ font-family: monospace; font-size: smaller;" width="100">
13 13
14 14
15$ ./busybox 15$ ./busybox
16BusyBox v1.00 (2004.04.06-14:56+0000) multi-call binary 16BusyBox v1.00 (2004.10.13-04:49+0000) multi-call binary
17 17
18Usage: busybox [function] [arguments]... 18Usage: busybox [function] [arguments]...
19 or: [function] [arguments]... 19 or: [function] [arguments]...
diff --git a/docs/busybox.net/shame.html b/docs/busybox.net/shame.html
index 849e73ce6..99807c17a 100644
--- a/docs/busybox.net/shame.html
+++ b/docs/busybox.net/shame.html
@@ -22,9 +22,13 @@ companies listed below should be ashamed of themselves. Furthermore, each
22product listed here is subject to being legally ordered to cease and desist 22product listed here is subject to being legally ordered to cease and desist
23distribution for violation of copyright law, and the distributor of each 23distribution for violation of copyright law, and the distributor of each
24product is subject to being sued for statutory copyright infringement damages 24product is subject to being sued for statutory copyright infringement damages
25plus legal fees. Nobody wants to be sued, and <a 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 has better things to do 26href="mailto:andersen@codepoet.org">Erik</a> certainly would prefer to spend
27than sue people. But he will sue if forced to do so to maintain compliance. 27his time doing better things than sue people. But he will sue if forced to
28do so to maintain compliance.
29
30<p>
31
28Do everyone a favor and don't break the law -- if you use busybox, comply with 32Do everyone a favor and don't break the law -- if you use busybox, comply with
29the busybox license by releasing the source code with your product. 33the busybox license by releasing the source code with your product.
30 34
@@ -32,7 +36,6 @@ the busybox license by releasing the source code with your product.
32 36
33<ul> 37<ul>
34 38
35 <li><a href="http://www.dlink.com/"> DLink - Model GSL-G604T, DSL-300T, and possibly other models</a>
36 <li><a href="http://www.trittontechnologies.com/products.html">Tritton Technologies NAS120</a> 39 <li><a href="http://www.trittontechnologies.com/products.html">Tritton Technologies NAS120</a>
37 <br>see <a href="http://www.ussg.iu.edu/hypermail/linux/kernel/0404.0/1611.html">here for details</a> 40 <br>see <a href="http://www.ussg.iu.edu/hypermail/linux/kernel/0404.0/1611.html">here for details</a>
38 <li><a href="http://www.macsense.com/product/homepod/">Macsense HomePod</a> 41 <li><a href="http://www.macsense.com/product/homepod/">Macsense HomePod</a>