emo/busybox
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

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

Browse Source 
easily.
This commit is contained in:
Bernhard Reutner-Fischer 2006-12-10 13:40:16 +00:00
parent 2ea630f9a5
commit 32f3ebf08f
1 changed files with 11 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
docs/busybox.net/FAQ.html
View File

@ -82,7 +82,8 @@ have additions to this FAQ document, we would love to add them,
to determine which applet to run, as shown above. to determine which applet to run, as shown above.
</p> </p>
<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 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 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 the command line "PATH= ./busybox ash". This will blank your command path
@ -96,7 +97,15 @@ have additions to this FAQ document, we would love to add them,
(So if you set it to /proc/self/exe, and happen to be able to chroot into (So if you set it to /proc/self/exe, and happen to be able to chroot into
your rootfs, you must mount /proc beforehand.) your rootfs, you must mount /proc beforehand.)
</p> </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 /> <hr />
<p> <p>
<h2><a name="configure">How do I configure busybox?</a></h2> <h2><a name="configure">How do I configure busybox?</a></h2>