svn commit: branches/busybox_scratch: docs/busybox.net
aldot at busybox.net
aldot at busybox.net
Wed Jun 21 18:55:18 UTC 2006
Author: aldot
Date: 2006-06-21 11:55:16 -0700 (Wed, 21 Jun 2006)
New Revision: 15466
Log:
- adjust docs to take CONFIG_BUSYBOX_EXEC_PATH into account.
Modified:
branches/busybox_scratch/INSTALL
branches/busybox_scratch/docs/busybox.net/FAQ.html
Changeset:
Modified: branches/busybox_scratch/INSTALL
===================================================================
--- branches/busybox_scratch/INSTALL 2006-06-21 18:48:06 UTC (rev 15465)
+++ branches/busybox_scratch/INSTALL 2006-06-21 18:55:16 UTC (rev 15466)
@@ -32,8 +32,10 @@
programs by that name. Supplying an empty command path (as above) means
the only commands busybox can find are the built-in ones.
-(Note that the standalone shell currently requires /proc/self/exe to
-launch new applets.)
+Note that the standalone shell requires CONFIG_BUSYBOX_EXEC_PATH
+to be set appropriately, depending on whether or not /proc/self/exe is
+available or not. If you do not have /proc, then point that config option
+to the location of your busybox binary, usually /bin/busybox.
Configuring Busybox:
====================
Modified: branches/busybox_scratch/docs/busybox.net/FAQ.html
===================================================================
--- branches/busybox_scratch/docs/busybox.net/FAQ.html 2006-06-21 18:48:06 UTC (rev 15465)
+++ branches/busybox_scratch/docs/busybox.net/FAQ.html 2006-06-21 18:55:16 UTC (rev 15466)
@@ -87,9 +87,13 @@
the command line "PATH= ./busybox ash". This will blank your command path
and run busybox as your command shell, so the only commands it can find
(without an explicit path such as /bin/ls) are the built-in busybox ones.
- This is another good way to see what's built into busybox. (Note that the
- standalone shell is dependent on the existence of /proc/self/exe, so before
- using it in a chroot environment you must mount /proc.)
+ This is another good way to see what's built into busybox.
+ Note that the standalone shell requires CONFIG_BUSYBOX_EXEC_PATH
+ to be set appropriately, depending on whether or not /proc/self/exe is
+ 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.)
</p>
<hr />
More information about the busybox-cvs
mailing list