aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/busybox.net/FAQ.html10
1 files changed, 7 insertions, 3 deletions
diff --git a/docs/busybox.net/FAQ.html b/docs/busybox.net/FAQ.html
index 34250a33e..fee207486 100644
--- a/docs/busybox.net/FAQ.html
+++ b/docs/busybox.net/FAQ.html
@@ -88,9 +88,13 @@ have additions to this FAQ document, we would love to add them,
88 the command line "PATH= ./busybox ash". This will blank your command path 88 the command line "PATH= ./busybox ash". This will blank your command path
89 and run busybox as your command shell, so the only commands it can find 89 and run busybox as your command shell, so the only commands it can find
90 (without an explicit path such as /bin/ls) are the built-in busybox ones. 90 (without an explicit path such as /bin/ls) are the built-in busybox ones.
91 This is another good way to see what's built into busybox. (Note that the 91 This is another good way to see what's built into busybox.
92 standalone shell is dependent on the existence of /proc/self/exe, so before 92 Note that the standalone shell requires CONFIG_BUSYBOX_EXEC_PATH
93 using it in a chroot environment you must mount /proc.) 93 to be set appropriately, depending on whether or not /proc/self/exe is
94 available or not. If you do not have /proc, then point that config option
95 to the location of your busybox binary, usually /bin/busybox.
96 (So if you set it to /proc/self/exe, and happen to be able to chroot into
97 your rootfs, you must mount /proc beforehand.)
94</p> 98</p>
95 99
96<hr /> 100<hr />