tweaked FAQ

Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>

1 files changed, 18 insertions, 12 deletions

diff --git a/FAQ.html b/FAQ.html
index 6416c34..8448505 100644
--- a/FAQ.html
+++ b/FAQ.html
@@ -461,26 +461,32 @@ and we're happy to respond to our users' needs.  But if you're coming to the
 list for free tech support we're going to ask you to upgrade to a current
 version before we try to diagnose your problem.</p>
 
-<p>If you don't want to take risk of replacing all applets by newer versions,
-you can employ this trick:</p>
+<p>If you're building BusyBox 0.50 with uClibc 0.9.19 and gcc 1.27 there's a
+fairly large chance that whatever problem you're seeing has already been fixed.
+To get that fix, all you have to do is upgrade to a newer version.  If you
+don't at least _try_ that, you're wasting our time.</p>
+
+<p>If you don't want to take the risk of replacing all applets by newer
+versions, you can employ this trick:</p>
 
 <p>Download most recent release, configure it with "make allnoconfig", then
 use menuconfig to switch on just the applet you want to test and maybe
-a couple of tuning options, compile that. Delete the old applet symlink
-that points to your old busybox, and replace it with the new busybox binary,
-renamed to applet's name.</p>
+a couple of tuning options. Then build busybox.</p>
 
-<p>Deleting the old symlink still leaves the old functionality in your existing
-old busybox binary, you just wouldn't be using it anymore.</p>
+<p>Then, on target system, delete the old applet symlink that points
+to your old busybox, and replace it with the new busybox binary, renamed
+to applet's name. In other words, if you want to replace only, say, httpd,
+then delete, say, /bin/httpd symlink (which points to your old busybox),
+then run "cp /path/to/new/busybox /bin/httpd". For some applets, you'll
+also need to "chmod u+s" it.</p>
 
 <p>Now you can test the new applet and post a more useful email to the mailing
 list, either "I see such and such bug even in latest release" or "I see such
-and such bug in release X.Y.Z, but it seems to be fixed".</p>
+and such bug in release X.Y.Z, but it seems to be fixed in last release".</p>
 
-<p>If you're building BusyBox 0.50 with uClibc 0.9.19 and gcc 1.27 there's a
-fairly large chance that whatever problem you're seeing has already been fixed.
-To get that fix, all you have to do is upgrade to a newer version.  If you
-don't at least _try_ that, you're wasting our time.</p>
+<p>Deleting the old symlink still leaves the old functionality in your existing
+old busybox binary, you just wouldn't be using it anymore. If things will
+get even worse with new version, you can always restore the symlink.</p>
 
 <p>The volunteers are happy to fix any bugs you point out in the current
 versions because doing so helps everybody and makes the project better.  We