diff options
author | Denys Vlasenko <vda.linux@googlemail.com> | 2010-01-13 22:43:13 +0100 |
---|---|---|
committer | Denys Vlasenko <vda.linux@googlemail.com> | 2010-01-13 22:43:13 +0100 |
commit | bb16f57e5d7a3985e27b684e1d329f88f896f40f (patch) | |
tree | aa276667f34f08c87023b1daee949248a70408e0 /INSTALL | |
parent | 4fc82e0067db4b54ee05d56feaa4fb981d380e5f (diff) | |
download | busybox-bb16f57e5d7a3985e27b684e1d329f88f896f40f.tar.gz |
INSTALL: update obsolete doc, as suggested by Doug Clapp (doug.clapp AT triad.rr.com)
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Diffstat (limited to 'INSTALL')
-rw-r--r-- | INSTALL | 20 |
1 files changed, 16 insertions, 4 deletions
@@ -19,11 +19,24 @@ it, is to enable all features and then use "standalone shell" mode with a blank command $PATH. To enable all features, use "make defconfig", which produces the largest -general-purpose configuration. (It's allyesconfig minus debugging options, +general-purpose configuration. It's allyesconfig minus debugging options, optional packaging choices, and a few special-purpose features requiring -extra configuration to use.) +extra configuration to use. Then enable "standalone shell" feature: make defconfig + make menuconfig + # select Busybox Settings + # then General Configuration + # then exec prefers applets + # exit back to top level menu + # select Shells + # then Standalone shell + # exit back to top level menu + # exit and save new configuration + # OR + # use these commands to modify .config directly: + sed -e 's/.*FEATURE_PREFER_APPLETS.*/CONFIG_FEATURE_PREFER_APPLETS=y/' -i .config + sed -e 's/.*FEATURE_SH_STANDALONE.*/CONFIG_FEATURE_SH_STANDALONE=y/' -i .config make PATH= ./busybox ash @@ -121,5 +134,4 @@ More Information: Se also the busybox FAQ, under the questions "How can I get started using BusyBox" and "How do I build a BusyBox-based system?" The BusyBox FAQ is -available from http://www.busybox.net/FAQ.html or as the file -docs/busybox.net/FAQ.html in this tarball. +available from http://www.busybox.net/FAQ.html |