|author||Denys Vlasenko <firstname.lastname@example.org>||2011-03-08 11:22:54 (GMT)|
|committer||Denys Vlasenko <email@example.com>||2011-03-08 11:22:54 (GMT)|
FAQ.html: small fix in "Standalone shell" subsection
Signed-off-by: Denys Vlasenko <firstname.lastname@example.org>
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.
A typical indication that you set CONFIG_BUSYBOX_EXEC_PATH to