From 075dd81c4460c027cf22800808993df3c07281f5 Mon Sep 17 00:00:00 2001 From: Eric Andersen Date: Wed, 7 Apr 2004 09:34:27 +0000 Subject: Remove the CONFIG_FEATURE_SH_APPLETS_ALWAYS_WIN option. It was sortof stupid and didn't work properly anyways. --- shell/Config.in | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) (limited to 'shell/Config.in') diff --git a/shell/Config.in b/shell/Config.in index 34baaa45c..b064ed41b 100644 --- a/shell/Config.in +++ b/shell/Config.in @@ -160,16 +160,14 @@ config CONFIG_FEATURE_SH_STANDALONE_SHELL default n depends on CONFIG_MSH || CONFIG_LASH || CONFIG_HUSH || CONFIG_ASH help - Have all the busybox commands built into the shell, creating - a standalone shell. - -config CONFIG_FEATURE_SH_APPLETS_ALWAYS_WIN - bool "Standalone shell -- applets always win" - default n - depends on CONFIG_FEATURE_SH_STANDALONE_SHELL - help - Use a command builtin to the shell over one with the same name, - that may be on the system. + This option causes the selected busybox shell to use busybox applets + in preference to executables in the PATH whenever possible. For + example, entering the command 'ifconfig' into the shell would cause + busybox to use the ifconfig busybox applet. Specifying the fully + qualified executable name, such as '/sbin/ifconfig' will still + execute the /sbin/ifconfig executable on the filesystem. This option + is generally used when creating a staticly linked version of busybox + for use as a rescue shell, in the event that you screw up your system. config CONFIG_FEATURE_COMMAND_EDITING bool "command line editing" -- cgit v1.2.3