summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDenys Vlasenko <vda.linux@googlemail.com>2013-07-13 22:38:02 (GMT)
committer Denys Vlasenko <vda.linux@googlemail.com>2013-07-13 22:38:02 (GMT)
commit17f12982952c002c06c6c5a17e635e3e8b4fb21f (patch)
treea4d1af516024394e84a997ae39f310900292461d
parent7c534017a572e285529c58a20b3dcf86a2d9aa9a (diff)
downloadbusybox-website-17f12982952c002c06c6c5a17e635e3e8b4fb21f.tar.gz
busybox-website-17f12982952c002c06c6c5a17e635e3e8b4fb21f.tar.bz2
FAQ: new "I have trouble installing Busybox on my phone" section
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
-rw-r--r--FAQ.html48
1 files changed, 48 insertions, 0 deletions
diff --git a/FAQ.html b/FAQ.html
index 68f9f25..f9ba6e7 100644
--- a/FAQ.html
+++ b/FAQ.html
@@ -27,6 +27,7 @@ have additions/corrections to this document, we would love to add them.
<h2>Troubleshooting</h2>
<ol>
<li><a href="#bugs">I think I found a bug in Busybox! What should I do?!</a></li>
+<li><a href="#mobile_dev_inst">I have trouble installing Busybox on my phone!</a></li>
<li><a href="#backporting">I'm using an ancient version from the dawn of time and something's broken. Can you backport fixes for free?</a></li>
<li><a href="#init">Busybox init isn't working!</a></li>
<li><a href="#emu">I am observing a bug in BusyBox on an obscure platform. Help.</a></li>
@@ -628,6 +629,53 @@ because of build timestamp and so on.
</p>
<hr />
+<h2><a name="mobile_dev_inst">I have trouble installing Busybox on my phone!</a></h2>
+
+<p>
+ Busybox mailing list and individual developers sometimes receive emails
+ which ask for help with Busybox installation on their smartphones,
+ tablets and the like.
+</p>
+<p>
+ Please note that at the time of this writing (2013-07), Busybox project
+ does not provide prebuilt binary packages for any architecture or device -
+ it provides the source code.
+</p>
+<p>
+ If you are downloading and installing a Busybox binary onto your device,
+ it means that someone else made that Busybox binary.
+ There are a number of people who do this (for example, Aboriginal Linux).
+</p>
+<p>
+ If you are experiencing problems with installing such a binary build,
+ you may be better off if you contact a person or a project which provides it,
+ not the Busybox development mailing list or an individual developer.
+ The link to project website and/or an email address of the build's author
+ is likely to be present on the same Web page where you downloaded
+ the binary package.
+</p>
+<p>
+ If you still want to seek advice about your problem on the Busybox
+ development mailing list, please provide as much information about
+ your situation as possible:
+<ul>
+<li>On what device you are trying to install the package?</li>
+<li>The URL to the place where you got the package from.</li>
+<li>The version of the package.</li>
+<li>The sequence of operations you are performing.</li>
+<li>What do you observe when you do that.</li>
+<li>In case it is not obvious from the previous description: What, in your opinion, is not happening correctly?</li>
+</ul>
+</p>
+<p>
+ Email like this: "I tried downloading applets for all version
+ of Busybox the problem remains consistent" will most likely
+ to be ignored, or you will be redirected to this FAQ.
+ (In this particular email example, <b>none</b> of the above
+ bits of information are present).
+</p>
+
+<hr />
<h2><a name="backporting">I'm using an ancient version from the dawn of time and something's broken. Can you backport fixes for free?</a></h2>
<p>Variants of this one get asked a lot.</p>