svn commit: trunk/busybox/docs/busybox.net

[aldot at busybox.net]

Author: aldot
Date: 2006-12-10 05:40:16 -0800 (Sun, 10 Dec 2006)
New Revision: 16833

Log:
- add an anchor to let me point people to FAQ.html#standalone_shell
  easily.


Modified:
   trunk/busybox/docs/busybox.net/FAQ.html


Changeset:
Modified: trunk/busybox/docs/busybox.net/FAQ.html
===================================================================
--- trunk/busybox/docs/busybox.net/FAQ.html	2006-12-10 13:24:03 UTC (rev 16832)
+++ trunk/busybox/docs/busybox.net/FAQ.html	2006-12-10 13:40:16 UTC (rev 16833)
@@ -82,7 +82,8 @@
     to determine which applet to run, as shown above.
 </p>
 <p>
-    BusyBox also has a feature called the "standalone shell", where the busybox
+    BusyBox also has a feature called the 
+    <a name="standalone_shell">"standalone shell"</a>, where the busybox
     shell runs any built-in applets before checking the command path.  This
     feature is also enabled by "make allyesconfig", and to try it out run
     the command line "PATH= ./busybox ash".  This will blank your command path
@@ -96,7 +97,15 @@
     (So if you set it to /proc/self/exe, and happen to be able to chroot into
     your rootfs, you must mount /proc beforehand.)
 </p>
-
+<p>
+    A typical indication that you set CONFIG_BUSYBOX_EXEC_PATH to proc but
+    forgot to mount proc is:
+<pre>
+$ /bin/echo $PATH
+/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11
+$ echo $PATH
+/bin/sh: echo: not found
+</pre>
 <hr />
 <p>
 <h2><a name="configure">How do I configure busybox?</a></h2>