diff options
| author | Denys Vlasenko <vda.linux@googlemail.com> | 2011-03-08 11:22:54 (GMT) |
|---|---|---|
| committer | Denys Vlasenko <vda.linux@googlemail.com> | 2011-03-08 11:22:54 (GMT) |
| commit | 9e8346f2057ba61bc3dc8e112eb07871f5384646 (patch) | |
| tree | 86cb6174cae5448d9b82eb7b4bea7bc5e71aa5c5 | |
| parent | a74be456323e4a66ba5782d6b37e48989d145cf0 (diff) | |
| download | busybox-website-9e8346f2057ba61bc3dc8e112eb07871f5384646.tar.gz busybox-website-9e8346f2057ba61bc3dc8e112eb07871f5384646.tar.bz2 | |
FAQ.html: small fix in "Standalone shell" subsection
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
| -rw-r--r-- | FAQ.html | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -280,10 +280,10 @@ have additions to this FAQ document, we would love to add them, Note that the standalone shell also requires CONFIG_BUSYBOX_EXEC_PATH to be set appropriately, and the default value, /proc/self/exe, would work only if /proc filesystem is mounted. - available or not. If you do not have /proc, then point that config option - to the location of your Busybox binary, usually /bin/busybox. (So if you set it to /proc/self/exe, and happen to be able to chroot into your rootfs, you must mount /proc beforehand.) + If you do not have /proc mouted, then point that config option + to the location of your Busybox binary, usually /bin/busybox. </p> <p> A typical indication that you set CONFIG_BUSYBOX_EXEC_PATH to |
