summaryrefslogtreecommitdiff
path: root/package/busybox/config/shell
diff options
context:
space:
mode:
authorWaldemar Brodkorb <wbx@openadk.org>2012-08-30 10:20:41 +0200
committerWaldemar Brodkorb <wbx@openadk.org>2012-08-30 10:20:41 +0200
commit46b42b19c7dec20400c1c7621d09277bf3d92874 (patch)
treea049bdbc56c981896da1131fcfb23ca178b1f255 /package/busybox/config/shell
parent8865b970f9db91f24472c596117c785cb76cdb2b (diff)
update busybox to latest stable version, refresh all Config.in files
Diffstat (limited to 'package/busybox/config/shell')
-rw-r--r--package/busybox/config/shell/Config.in261
1 files changed, 145 insertions, 116 deletions
diff --git a/package/busybox/config/shell/Config.in b/package/busybox/config/shell/Config.in
index 674aaabbe..52a96c7e2 100644
--- a/package/busybox/config/shell/Config.in
+++ b/package/busybox/config/shell/Config.in
@@ -1,3 +1,4 @@
+# DO NOT EDIT. This file is generated from Config.src
#
# For a description of the syntax of this configuration file,
# see scripts/kbuild/config-language.txt.
@@ -5,58 +6,6 @@
menu "Shells"
-choice
- prompt "Choose which shell is aliased to 'sh' name"
- default FEATURE_SH_IS_ASH
- help
- Choose a shell. The ash shell is the most bash compatible
- and full featured one.
-
-config BUSYBOX_FEATURE_SH_IS_ASH
- select BUSYBOX_ASH
- bool "ash"
- depends on !BUSYBOX_NOMMU
-
-config BUSYBOX_FEATURE_SH_IS_HUSH
- select BUSYBOX_HUSH
- bool "hush"
-
-config BUSYBOX_FEATURE_SH_IS_NONE
- bool "none"
-
-endchoice
-
-choice
- prompt "Choose which shell is aliased to 'bash' name"
- default BUSYBOX_FEATURE_BASH_IS_NONE
- help
- Choose which shell you want to be executed by 'bash' alias.
- The ash shell is the most bash compatible and full featured one.
-
- Note that selecting this option does not switch on any bash
- compatibility code. It merely makes it possible to install
- /bin/bash (sym)link and run scripts which start with
- #!/bin/bash line.
-
- Many systems use it in scripts which use bash-specific features,
- even simple ones like $RANDOM. Without this option, busybox
- can't be used for running them because it won't recongnize
- "bash" as a supported applet name.
-
-config BUSYBOX_FEATURE_BASH_IS_ASH
- depends on BUSYBOX_ASH
- bool "ash"
- depends on !BUSYBOX_NOMMU
-
-config BUSYBOX_FEATURE_BASH_IS_HUSH
- depends on BUSYBOX_HUSH
- bool "hush"
-
-config BUSYBOX_FEATURE_BASH_IS_NONE
- bool "none"
-
-endchoice
-
config BUSYBOX_ASH
bool "ash"
default y
@@ -75,6 +24,13 @@ config BUSYBOX_ASH_BASH_COMPAT
help
Enable bash-compatible extensions.
+config BUSYBOX_ASH_IDLE_TIMEOUT
+ bool "Idle timeout variable"
+ default n
+ depends on BUSYBOX_ASH
+ help
+ Enables bash-like auto-logout after $TMOUT seconds of idle time.
+
config BUSYBOX_ASH_JOB_CONTROL
bool "Job control"
default y
@@ -83,7 +39,7 @@ config BUSYBOX_ASH_JOB_CONTROL
Enable job control in the ash shell.
config BUSYBOX_ASH_ALIAS
- bool "alias support"
+ bool "Alias support"
default y
depends on BUSYBOX_ASH
help
@@ -94,32 +50,32 @@ config BUSYBOX_ASH_GETOPTS
default y
depends on BUSYBOX_ASH
help
- Enable getopts builtin in the ash shell.
+ Enable support for getopts builtin in ash.
config BUSYBOX_ASH_BUILTIN_ECHO
bool "Builtin version of 'echo'"
default y
depends on BUSYBOX_ASH
help
- Enable support for echo, builtin to ash.
+ Enable support for echo builtin in ash.
config BUSYBOX_ASH_BUILTIN_PRINTF
bool "Builtin version of 'printf'"
default y
depends on BUSYBOX_ASH
help
- Enable support for printf, builtin to ash.
+ Enable support for printf builtin in ash.
config BUSYBOX_ASH_BUILTIN_TEST
bool "Builtin version of 'test'"
default y
depends on BUSYBOX_ASH
help
- Enable support for test, builtin to ash.
+ Enable support for test builtin in ash.
config BUSYBOX_ASH_CMDCMD
bool "'command' command to override shell builtins"
- default n
+ default y
depends on BUSYBOX_ASH
help
Enable support for the ash 'command' builtin, which allows
@@ -131,7 +87,7 @@ config BUSYBOX_ASH_MAIL
default n
depends on BUSYBOX_ASH
help
- Enable "check for new mail" in the ash shell.
+ Enable "check for new mail" function in the ash shell.
config BUSYBOX_ASH_OPTIMIZE_FOR_SIZE
bool "Optimize for size instead of speed"
@@ -142,7 +98,7 @@ config BUSYBOX_ASH_OPTIMIZE_FOR_SIZE
config BUSYBOX_ASH_RANDOM_SUPPORT
bool "Pseudorandom generator and $RANDOM variable"
- default n
+ default y
depends on BUSYBOX_ASH
help
Enable pseudorandom generator and dynamic variable "$RANDOM".
@@ -160,6 +116,49 @@ config BUSYBOX_ASH_EXPAND_PRMT
This option recreates the prompt string from the environment
variable each time it is displayed.
+config BUSYBOX_CTTYHACK
+ bool "cttyhack"
+ default n
+ help
+ One common problem reported on the mailing list is the "can't
+ access tty; job control turned off" error message, which typically
+ appears when one tries to use a shell with stdin/stdout on
+ /dev/console.
+ This device is special - it cannot be a controlling tty.
+
+ The proper solution is to use the correct device instead of
+ /dev/console.
+
+ cttyhack provides a "quick and dirty" solution to this problem.
+ It analyzes stdin with various ioctls, trying to determine whether
+ it is a /dev/ttyN or /dev/ttySN (virtual terminal or serial line).
+ On Linux it also checks sysfs for a pointer to the active console.
+ If cttyhack is able to find the real console device, it closes
+ stdin/out/err and reopens that device.
+ Then it executes the given program. Opening the device will make
+ that device a controlling tty. This may require cttyhack
+ to be a session leader.
+
+ Example for /etc/inittab (for busybox init):
+
+ ::respawn:/bin/cttyhack /bin/sh
+
+ Starting an interactive shell from boot shell script:
+
+ setsid cttyhack sh
+
+ Giving controlling tty to shell running with PID 1:
+
+ # exec cttyhack sh
+
+ Without cttyhack, you need to know exact tty name,
+ and do something like this:
+
+ # exec setsid sh -c 'exec sh </dev/tty1 >/dev/tty1 2>&1'
+
+ Starting getty on a controlling tty from a shell script:
+
+ # getty 115200 $(cttyhack)
config BUSYBOX_HUSH
bool "hush"
default n
@@ -190,7 +189,7 @@ config BUSYBOX_HUSH_BRACE_EXPANSION
config BUSYBOX_HUSH_HELP
bool "help builtin"
- default n
+ default y
depends on BUSYBOX_HUSH
help
Enable help builtin in hush. Code size + ~1 kbyte.
@@ -214,7 +213,7 @@ config BUSYBOX_HUSH_SAVEHISTORY
config BUSYBOX_HUSH_JOB
bool "Job control"
- default n
+ default y
depends on BUSYBOX_HUSH_INTERACTIVE
help
Enable job control: Ctrl-Z backgrounds, Ctrl-C interrupts current
@@ -225,61 +224,61 @@ config BUSYBOX_HUSH_JOB
config BUSYBOX_HUSH_TICK
bool "Process substitution"
- default n
+ default y
depends on BUSYBOX_HUSH
help
Enable process substitution `command` and $(command) in hush.
config BUSYBOX_HUSH_IF
bool "Support if/then/elif/else/fi"
- default n
+ default y
depends on BUSYBOX_HUSH
help
Enable if/then/elif/else/fi in hush.
config BUSYBOX_HUSH_LOOPS
bool "Support for, while and until loops"
- default n
+ default y
depends on BUSYBOX_HUSH
help
Enable for, while and until loops in hush.
config BUSYBOX_HUSH_CASE
bool "Support case ... esac statement"
- default n
+ default y
depends on BUSYBOX_HUSH
help
Enable case ... esac statement in hush. +400 bytes.
config BUSYBOX_HUSH_FUNCTIONS
bool "Support funcname() { commands; } syntax"
- default n
+ default y
depends on BUSYBOX_HUSH
help
Enable support for shell functions in hush. +800 bytes.
config BUSYBOX_HUSH_LOCAL
bool "Support local builtin"
- default n
+ default y
depends on BUSYBOX_HUSH_FUNCTIONS
help
Enable support for local variables in functions.
-config BUSYBOX_HUSH_EXPORT_N
- bool "Support 'export -n' option"
- default n
- depends on BUSYBOX_HUSH
- help
- export -n unexports variables. It is a bash extension.
-
config BUSYBOX_HUSH_RANDOM_SUPPORT
bool "Pseudorandom generator and $RANDOM variable"
- default n
+ default y
depends on BUSYBOX_HUSH
help
Enable pseudorandom generator and dynamic variable "$RANDOM".
Each read of "$RANDOM" will generate a new pseudorandom value.
+config BUSYBOX_HUSH_EXPORT_N
+ bool "Support 'export -n' option"
+ default y
+ depends on BUSYBOX_HUSH
+ help
+ export -n unexports variables. It is a bash extension.
+
config BUSYBOX_HUSH_MODE_X
bool "Support 'hush -x' option and 'set -x' command"
default y
@@ -296,6 +295,61 @@ config BUSYBOX_MSH
msh is deprecated and will be removed, please migrate to hush.
+
+choice
+ prompt "Choose which shell is aliased to 'sh' name"
+ default FEATURE_SH_IS_ASH
+ help
+ Choose which shell you want to be executed by 'sh' alias.
+ The ash shell is the most bash compatible and full featured one.
+
+# note: cannot use "select ASH" here, it breaks "make allnoconfig"
+config BUSYBOX_FEATURE_SH_IS_ASH
+ depends on BUSYBOX_ASH
+ bool "ash"
+ depends on !BUSYBOX_NOMMU
+
+config BUSYBOX_FEATURE_SH_IS_HUSH
+ depends on BUSYBOX_HUSH
+ bool "hush"
+
+config BUSYBOX_FEATURE_SH_IS_NONE
+ bool "none"
+
+endchoice
+
+choice
+ prompt "Choose which shell is aliased to 'bash' name"
+ default FEATURE_BASH_IS_NONE
+ help
+ Choose which shell you want to be executed by 'bash' alias.
+ The ash shell is the most bash compatible and full featured one.
+
+ Note that selecting this option does not switch on any bash
+ compatibility code. It merely makes it possible to install
+ /bin/bash (sym)link and run scripts which start with
+ #!/bin/bash line.
+
+ Many systems use it in scripts which use bash-specific features,
+ even simple ones like $RANDOM. Without this option, busybox
+ can't be used for running them because it won't recongnize
+ "bash" as a supported applet name.
+
+config BUSYBOX_FEATURE_BASH_IS_ASH
+ depends on BUSYBOX_ASH
+ bool "ash"
+ depends on !BUSYBOX_NOMMU
+
+config BUSYBOX_FEATURE_BASH_IS_HUSH
+ depends on BUSYBOX_HUSH
+ bool "hush"
+
+config BUSYBOX_FEATURE_BASH_IS_NONE
+ bool "none"
+
+endchoice
+
+
config BUSYBOX_SH_MATH_SUPPORT
bool "POSIX math support"
default y
@@ -305,7 +359,7 @@ config BUSYBOX_SH_MATH_SUPPORT
config BUSYBOX_SH_MATH_SUPPORT_64
bool "Extend POSIX math support to 64 bit"
- default n
+ default y
depends on BUSYBOX_SH_MATH_SUPPORT
help
Enable 64-bit math support in the shell. This will make the shell
@@ -314,8 +368,8 @@ config BUSYBOX_SH_MATH_SUPPORT_64
config BUSYBOX_FEATURE_SH_EXTRA_QUIET
bool "Hide message on interactive shell startup"
- default n
- depends on BUSYBOX_MSH || BUSYBOX_LASH || BUSYBOX_HUSH || BUSYBOX_ASH
+ default y
+ depends on BUSYBOX_HUSH || BUSYBOX_ASH
help
Remove the busybox introduction when starting a shell.
@@ -357,9 +411,9 @@ config BUSYBOX_FEATURE_SH_NOFORK
default n
depends on (BUSYBOX_HUSH || BUSYBOX_ASH) && BUSYBOX_FEATURE_PREFER_APPLETS
help
- This option causes busybox shells [currently only ash]
- to not execute typical fork/exec/wait sequence, but call <applet>_main
- directly, if possible. (Sometimes it is not possible: for example,
+ This option causes busybox shells to not execute typical
+ fork/exec/wait sequence, but call <applet>_main directly,
+ if possible. (Sometimes it is not possible: for example,
this is not possible in pipes).
This will be done only for some applets (those which are marked
@@ -367,42 +421,17 @@ config BUSYBOX_FEATURE_SH_NOFORK
This may significantly speed up some shell scripts.
- This feature is relatively new. Use with care.
+ This feature is relatively new. Use with care. Report bugs
+ to project mailing list.
-config BUSYBOX_CTTYHACK
- bool "cttyhack"
- default n
+config BUSYBOX_FEATURE_SH_HISTFILESIZE
+ bool "Use $HISTFILESIZE"
+ default y
+ depends on BUSYBOX_HUSH || BUSYBOX_ASH
help
- One common problem reported on the mailing list is "can't access tty;
- job control turned off" error message which typically appears when
- one tries to use shell with stdin/stdout opened to /dev/console.
- This device is special - it cannot be a controlling tty.
-
- Proper solution is to use correct device instead of /dev/console.
-
- cttyhack provides "quick and dirty" solution to this problem.
- It analyzes stdin with various ioctls, trying to determine whether
- it is a /dev/ttyN or /dev/ttySN (virtual terminal or serial line).
- If it detects one, it closes stdin/out/err and reopens that device.
- Then it executes given program. Opening the device will make
- that device a controlling tty. This may require cttyhack
- to be a session leader.
-
- Example for /etc/inittab (for busybox init):
-
- ::respawn:/bin/cttyhack /bin/sh
+ This option makes busybox shells to use $HISTFILESIZE variable
+ to set shell history size. Note that its max value is capped
+ by "History size" setting in library tuning section.
- Starting an interactive shell from boot shell script:
-
- setsid cttyhack sh
-
- Giving controlling tty to shell running with PID 1:
-
- # exec cttyhack sh
-
- Without cttyhack, you need to know exact tty name,
- and do something like this:
-
- # exec setsid sh -c 'exec sh </dev/tty1 >/dev/tty1 2>&1'
endmenu