diff options
author | Eric Andersen <andersen@codepoet.org> | 2004-10-08 10:50:08 +0000 |
---|---|---|
committer | Eric Andersen <andersen@codepoet.org> | 2004-10-08 10:50:08 +0000 |
commit | 6c4a6b1a231a04d2993615885139a43f4294b96f (patch) | |
tree | 7e9e21eb75a724e4b5a00d9be62c076b03222ec4 | |
parent | ad63cb25140996588f223b009b094f1408a52a4b (diff) | |
download | busybox-w32-6c4a6b1a231a04d2993615885139a43f4294b96f.tar.gz busybox-w32-6c4a6b1a231a04d2993615885139a43f4294b96f.tar.bz2 busybox-w32-6c4a6b1a231a04d2993615885139a43f4294b96f.zip |
Add an initial FAQ
-rw-r--r-- | docs/busybox.net/FAQ.html | 302 | ||||
-rw-r--r-- | docs/busybox.net/header.html | 1 |
2 files changed, 303 insertions, 0 deletions
diff --git a/docs/busybox.net/FAQ.html b/docs/busybox.net/FAQ.html new file mode 100644 index 000000000..70c1a9014 --- /dev/null +++ b/docs/busybox.net/FAQ.html | |||
@@ -0,0 +1,302 @@ | |||
1 | <!--#include file="header.html" --> | ||
2 | |||
3 | |||
4 | <h3>Frequently Asked Questions</h3> | ||
5 | |||
6 | This is a collection of some of the more frequently asked questions | ||
7 | about BusyBox. Some of the questions even have answers. If you | ||
8 | have 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 <favorite feature> 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="#helpme">I need help with BusyBox! What should I do?</a> | ||
22 | <li><a href="#contracts">I need you to add <favorite feature>! Are the BusyBox developers willing to | ||
23 | be paid in order to fix bugs or add in <favorite feature>? Are you willing to provide | ||
24 | support contracts?</a> | ||
25 | <li><a href="#support">I think you guys are great and I want to help support your work!</a> | ||
26 | |||
27 | |||
28 | </ol> | ||
29 | |||
30 | |||
31 | <hr /> | ||
32 | <p> | ||
33 | <h2><a name="kernel">Which Linux kernel versions are supported?</a></h2> | ||
34 | <p> | ||
35 | |||
36 | |||
37 | Full functionality requires Linux 2.2.x or better. A large fraction of the | ||
38 | code should run on just about anything. While the current code is fairly | ||
39 | Linux specific, it should be fairly easy to port the majority of the code | ||
40 | to support, say, FreeBSD or Solaris, or Mac OS X, or even Windows (if you | ||
41 | are into that sort of thing). | ||
42 | |||
43 | |||
44 | <hr /> | ||
45 | <p> | ||
46 | <h2><a name="arch">Which architectures does BusyBox run on?</a></h2> | ||
47 | <p> | ||
48 | |||
49 | |||
50 | BusyBox in general will build on any architecture supported by gcc. | ||
51 | Kernel module loading for 2.2 and 2.4 Linux kernels is currently | ||
52 | limited to ARM, CRIS, H8/300, x86, ia64, x86_64, m68k, MIPS, PowerPC, | ||
53 | S390, SH3/4/5, Sparc, v850e, and x86_64 for 2.4.x kernels. | ||
54 | |||
55 | With 2.6.x kernels, module loading support should work on all architectures. | ||
56 | |||
57 | |||
58 | <hr /> | ||
59 | <p> | ||
60 | <h2><a name="libc">Which C libraries are supported?</a></h2> | ||
61 | <p> | ||
62 | |||
63 | |||
64 | uClibc and glibc are supported. People have been looking at newlib and | ||
65 | dietlibc, but they are currently considered unsupported, untested, or | ||
66 | worse. Linux-libc5 is no longer supported. If you require a small C | ||
67 | library, you should probably use uClibc. | ||
68 | |||
69 | |||
70 | <hr /> | ||
71 | <p> | ||
72 | <h2><a name="commercial">Can I include BusyBox as part of the software on my device?</a> | ||
73 | |||
74 | Yes. As long as you <a href="http://busybox.net/license.html">fully comply | ||
75 | with the generous terms of the GPL BusyBox license</a> you can ship BusyBox | ||
76 | as part of the software on your device. | ||
77 | |||
78 | <a href="#support">Please consider sharing some of the money you make.</a> | ||
79 | |||
80 | |||
81 | <hr /> | ||
82 | <p> | ||
83 | <h2><a name="bugs">I think I found a bug in BusyBox! What should I do?</h2> | ||
84 | <p> | ||
85 | |||
86 | If you find a problem with BusyBox, please submit a detailed bug report to | ||
87 | the BusyBox mailing list at <a href="mailto:busybox@mail.busybox.net"> | ||
88 | busybox@mail.busybox.net</a>. Please do not send private email to Erik | ||
89 | (the maintainer of BusyBox) asking for private help unless you are planning | ||
90 | on paying for consulting services. When we answer questions on the BusyBox | ||
91 | mailing list, it helps everyone, while private answers help only you... | ||
92 | |||
93 | <p> | ||
94 | |||
95 | If you find bugs, please submit a detailed bug report to the BusyBox mailing | ||
96 | list at busybox@mail.busybox.net. A well-written bug report should include a | ||
97 | transcript of a shell session that demonstrates the bad behavior and enables | ||
98 | anyone else to duplicate the bug on their own machine. The following is such | ||
99 | an example: | ||
100 | |||
101 | <pre> | ||
102 | To: busybox@mail.busybox.net | ||
103 | From: diligent@testing.linux.org | ||
104 | Subject: /bin/date doesn't work | ||
105 | |||
106 | Package: BusyBox | ||
107 | Version: 1.00 | ||
108 | |||
109 | When I execute BusyBox 'date' it produces unexpected results. | ||
110 | With GNU date I get the following output: | ||
111 | |||
112 | $ date | ||
113 | Fri Oct 8 14:19:41 MDT 2004 | ||
114 | |||
115 | But when I use BusyBox date I get this instead: | ||
116 | |||
117 | $ date | ||
118 | illegal instruction | ||
119 | |||
120 | I am using Debian unstable, kernel version 2.4.27 on a x86 system, | ||
121 | and the latest uClibc from CVS. Thanks for the wonderful program! | ||
122 | |||
123 | -Diligent | ||
124 | </pre> | ||
125 | |||
126 | Note the careful description and use of examples showing not only what BusyBox | ||
127 | does, but also a counter example showing what an equivalent GNU app does. Bug | ||
128 | reports lacking proper detail may never be fixed... Thanks for understanding. | ||
129 | |||
130 | <hr /> | ||
131 | <p> | ||
132 | <h2><a name="job_control">Why do I keep getting "sh: can't access tty; job control | ||
133 | turned off" errors? Why doesn't Control-C work within my shell?</a></h2> | ||
134 | <p> | ||
135 | |||
136 | Job control will be turned off since your shell can not obtain a controlling | ||
137 | terminal. This typically happens when you run your shell on /dev/console. | ||
138 | The kernel will not provide a controlling terminal on the /dev/console | ||
139 | device. Your should run your shell on a normal tty such as tty1 or ttyS0 | ||
140 | and everything will work perfectly. If you <em>REALLY</em> want your shell | ||
141 | to run on /dev/console, then you can hack your kernel (if you are into that | ||
142 | sortof thing) by changing drivers/char/tty_io.c to change the lines where | ||
143 | it sets "noctty = 1;" to instead set it to "0". I recommend you instead | ||
144 | run your shell on a real console... | ||
145 | |||
146 | |||
147 | <hr /> | ||
148 | <p> | ||
149 | <h2><a name="demanding">I demand that you to add <favorite feature> right now! How come | ||
150 | 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> | ||
152 | <p> | ||
153 | |||
154 | You have not paid us a single cent and yet you still have the product of | ||
155 | many years of our work. We are not your slaves! We work on BusyBox | ||
156 | because we find it useful and interesting. If you go off flaming us, we | ||
157 | will ignore you. | ||
158 | |||
159 | |||
160 | <hr /> | ||
161 | <p> | ||
162 | <h2><a name="helpme">I need help with BusyBox! What should I do?</a></h2> | ||
163 | <p> | ||
164 | |||
165 | If you find that you need help with BusyBox, you can ask for help on the | ||
166 | BusyBox mailing list at busybox@mail.busybox.net. In addition to the BusyBox | ||
167 | mailing list, Erik (andersee), Manuel (mjn3) and others are known to hang out | ||
168 | on the uClibc IRC channel: #uclibc on irc.freenode.net. | ||
169 | |||
170 | <p> | ||
171 | |||
172 | <b>Please do not send private email to Erik, Manuel, or the other BusyBox | ||
173 | contributors asking for private help unless you are planning on paying for | ||
174 | consulting services.</b> | ||
175 | |||
176 | <p> | ||
177 | |||
178 | When we answer questions on the BusyBox mailing list, it helps everyone | ||
179 | since people with similar problems in the future will be able to get help | ||
180 | by searching the mailing list archives. Private help is reserved as a paid | ||
181 | service. If you need to use private communication, or if you are serious | ||
182 | about getting timely assistance with BusyBox, you should seriously consider | ||
183 | paying for consulting services. | ||
184 | |||
185 | <p> | ||
186 | |||
187 | |||
188 | |||
189 | <hr /> | ||
190 | <p> | ||
191 | <h2><a name="contracts">I need you to add <favorite feature>! Are the BusyBox | ||
192 | developers willing to be paid in order to fix bugs or add in <favorite feature>? | ||
193 | Are you willing to provide support contracts?</a></h2> | ||
194 | <p> | ||
195 | |||
196 | Sure! Now you have our attention! What you should do is contact <a | ||
197 | href="mailto:andersen@codepoet.org">Erik Andersen</a> of <a | ||
198 | 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 | ||
200 | 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, | ||
202 | and may even ask you to post your request for services on the mailing list. | ||
203 | |||
204 | |||
205 | <hr /> | ||
206 | <p> | ||
207 | <h2><a name="support">I think you guys are great and I want to help support your work!</a></h2> | ||
208 | <p> | ||
209 | |||
210 | Wow, that would be great! Erik personally pays for all the bandwidth, and | ||
211 | all servers used for busybox.net out of his own pocket. If you would like | ||
212 | to make a donation to help support BusyBox, and/or request features, you | ||
213 | can click here: | ||
214 | |||
215 | <!-- Begin PayPal Logo --> | ||
216 | <center> | ||
217 | <form action="https://www.paypal.com/cgi-bin/webscr" method="post"> | ||
218 | <input type="hidden" name="cmd" value="_xclick"> | ||
219 | <input type="hidden" name="business" value="andersen@codepoet.org"> | ||
220 | <input type="hidden" name="item_name" value="Support BusyBox"> | ||
221 | <input type="hidden" name="image_url" value="https://codepoet-consulting.com/images/codepoet.png"> | ||
222 | <input type="hidden" name="no_shipping" value="1"> | ||
223 | <input type="image" src="images/donate.png" name="submit" alt="Make donation using PayPal"> | ||
224 | </form> | ||
225 | </center> | ||
226 | <!-- End PayPal Logo --> | ||
227 | |||
228 | If you prefer to contact Erik directly to make a donation, donate hardware, | ||
229 | request support, etc, you can contact | ||
230 | <a href="http://codepoet-consulting.com/">CodePoet Consulting</a> here. | ||
231 | CodePoet Consulting can accept both Visa and MasterCard for those that do not | ||
232 | trust PayPal... | ||
233 | |||
234 | <hr /> | ||
235 | |||
236 | <br> | ||
237 | <br> | ||
238 | <br> | ||
239 | <br> | ||
240 | <br> | ||
241 | <br> | ||
242 | <br> | ||
243 | <br> | ||
244 | <br> | ||
245 | <br> | ||
246 | <br> | ||
247 | <br> | ||
248 | <br> | ||
249 | <br> | ||
250 | <br> | ||
251 | <br> | ||
252 | <br> | ||
253 | <br> | ||
254 | <br> | ||
255 | <br> | ||
256 | <br> | ||
257 | <br> | ||
258 | <br> | ||
259 | <br> | ||
260 | <br> | ||
261 | <br> | ||
262 | <br> | ||
263 | <br> | ||
264 | <br> | ||
265 | <br> | ||
266 | <br> | ||
267 | <br> | ||
268 | <br> | ||
269 | <br> | ||
270 | <br> | ||
271 | <br> | ||
272 | <br> | ||
273 | <br> | ||
274 | <br> | ||
275 | <br> | ||
276 | <br> | ||
277 | <br> | ||
278 | <br> | ||
279 | <br> | ||
280 | <br> | ||
281 | <br> | ||
282 | <br> | ||
283 | <br> | ||
284 | <br> | ||
285 | <br> | ||
286 | <br> | ||
287 | <br> | ||
288 | <br> | ||
289 | <br> | ||
290 | <br> | ||
291 | <br> | ||
292 | <br> | ||
293 | <br> | ||
294 | <br> | ||
295 | <br> | ||
296 | <br> | ||
297 | <br> | ||
298 | <br> | ||
299 | <br> | ||
300 | |||
301 | <!--#include file="footer.html" --> | ||
302 | |||
diff --git a/docs/busybox.net/header.html b/docs/busybox.net/header.html index 33638f322..77c141832 100644 --- a/docs/busybox.net/header.html +++ b/docs/busybox.net/header.html | |||
@@ -48,6 +48,7 @@ | |||
48 | <br><a href="/lists.html">Mailing Lists</a> | 48 | <br><a href="/lists.html">Mailing Lists</a> |
49 | <br><a href="/news.html">Latest News</a> | 49 | <br><a href="/news.html">Latest News</a> |
50 | <br><a href="/download.html">Download</a> | 50 | <br><a href="/download.html">Download</a> |
51 | <br><a href="/FAQ.html">FAQ</a> | ||
51 | <br><a href="/cvs_anon.html">Accessing CVS</a> | 52 | <br><a href="/cvs_anon.html">Accessing CVS</a> |
52 | <br><a href="/cgi-bin/cvsweb/busybox/">Browse CVS</a> | 53 | <br><a href="/cgi-bin/cvsweb/busybox/">Browse CVS</a> |
53 | <br><a href="/docs.html">Documentation</a> | 54 | <br><a href="/docs.html">Documentation</a> |