2 # For a description of the syntax of this configuration file,
3 # see scripts/kbuild/config-language.txt.
9 prompt "Choose your default shell"
10 default FEATURE_SH_IS_NONE
12 Choose a shell. The ash shell is the most bash compatible
13 and full featured one.
15 config FEATURE_SH_IS_ASH
19 config FEATURE_SH_IS_HUSH
23 ####config FEATURE_SH_IS_LASH
27 config FEATURE_SH_IS_MSH
31 config FEATURE_SH_IS_NONE
40 Tha 'ash' shell adds about 60k in the default configuration and is
41 the most complete and most pedantically correct shell included with
42 busybox. This shell is actually a derivative of the Debian 'dash'
43 shell (by Herbert Xu), which was created by porting the 'ash' shell
44 (written by Kenneth Almquist) from NetBSD.
46 comment "Ash Shell Options"
49 config ASH_BASH_COMPAT
50 bool "bash-compatible extensions"
54 Enable bash-conpatible extensions.
56 config ASH_JOB_CONTROL
61 Enable job control in the ash shell.
63 config ASH_READ_NCHARS
64 bool "'read -n N' and 'read -s' support"
68 'read -n N' will return a value after N characters have been read.
69 'read -s' will read without echoing the user's input.
71 config ASH_READ_TIMEOUT
72 bool "'read -t S' support"
76 'read -t S' will return a value after S seconds have passed.
77 This implementation will allow fractional seconds, expressed
78 as a decimal fraction, e.g. 'read -t 2.5 foo'.
85 Enable alias support in the ash shell.
87 config ASH_MATH_SUPPORT
88 bool "Posix math support"
92 Enable math support in the ash shell.
94 config ASH_MATH_SUPPORT_64
95 bool "Extend Posix math support to 64 bit"
97 depends on ASH_MATH_SUPPORT
99 Enable 64-bit math support in the ash shell. This will make
100 the shell slightly larger, but will allow computation with very
104 bool "Builtin getopt to parse positional parameters"
108 Enable getopts builtin in the ash shell.
110 config ASH_BUILTIN_ECHO
111 bool "Builtin version of 'echo'"
115 Enable support for echo, builtin to ash.
117 config ASH_BUILTIN_PRINTF
118 bool "Builtin version of 'printf'"
122 Enable support for printf, builtin to ash.
124 config ASH_BUILTIN_TEST
125 bool "Builtin version of 'test'"
129 Enable support for test, builtin to ash.
132 bool "'command' command to override shell builtins"
136 Enable support for the ash 'command' builtin, which allows
137 you to run the specified command with the specified arguments,
138 even when there is an ash builtin command with the same name.
141 bool "Check for new mail on interactive shells"
145 Enable "check for new mail" in the ash shell.
147 config ASH_OPTIMIZE_FOR_SIZE
148 bool "Optimize for size instead of speed"
152 Compile ash for reduced size at the price of speed.
154 config ASH_RANDOM_SUPPORT
155 bool "Pseudorandom generator and variable $RANDOM"
159 Enable pseudorandom generator and dynamic variable "$RANDOM".
160 Each read of "$RANDOM" will generate a new pseudorandom value.
161 You can reset the generator by using a specified start value.
162 After "unset RANDOM" then generator will switch off and this
163 variable will no longer have special treatment.
165 config ASH_EXPAND_PRMT
166 bool "Expand prompt string"
170 "PS#" may be contain volatile content, such as backquote commands.
171 This option recreates the prompt string from the environment
172 variable each time it is displayed.
178 hush is a very small shell (just 18k) and it has fairly complete
179 Bourne shell grammar. It even handles all the normal flow control
180 options such as if/then/elif/else/fi, for/in/do/done, while loops,
183 It uses only vfork, so it can be used on uClinux systems.
185 It does not handle select, functions, here documents ( <<
186 word ), arithmetic expansion, aliases, brace expansion, tilde
187 expansion, &> and >& redirection of stdout+stderr, etc.
194 Enable help builtin in hush. Code size + ~1 kbyte.
196 config HUSH_INTERACTIVE
197 bool "Interactive mode"
201 Enable interactive mode (prompt and command editing).
202 Without this, hush simply reads and executes commands
203 from stdin just like a shell script from the file.
204 No prompt, no PS1/PS2 magic shell variables.
209 depends on HUSH_INTERACTIVE
211 Enable job control: Ctrl-Z backgrounds, Ctrl-C interrupts current
212 command (not entire shell), fg/bg builtins work. Without this option,
213 "cmd &" still works by simply spawning a process and immediately
214 prompting for next command (or executing next command in a script),
215 but no separate process group is formed.
218 bool "Process substitution"
222 Enable process substitution `command` and $(command) in hush.
225 bool "Support if/then/elif/else/fi"
229 Enable if/then/elif/else/fi in hush.
232 bool "Support for, while and until loops"
236 Enable for, while and until loops in hush.
237 As of 2008-07, break and continue statements are not supported.
240 bool "Support case ... esac statement"
244 Enable case ... esac statement in hush. +400 bytes.
251 lash is deprecated and will be removed, please migrate to hush.
257 The minix shell (adds just 30k) is quite complete and handles things
258 like for/do/done, case/esac and all the things you expect a Bourne
259 shell to do. It is not always pedantically correct about Bourne
260 shell grammar (try running the shell testscript "tests/sh.testcases"
261 on it and compare vs bash) but for most things it works quite well.
262 It uses only vfork, so it can be used on uClinux systems.
264 comment "Bourne Shell Options"
265 depends on MSH || LASH || HUSH || ASH
267 config FEATURE_SH_EXTRA_QUIET
268 bool "Hide message on interactive shell startup"
270 depends on MSH || LASH || HUSH || ASH
272 Remove the busybox introduction when starting a shell.
274 config FEATURE_SH_STANDALONE
275 bool "Standalone shell"
277 depends on (MSH || LASH || HUSH || ASH) && FEATURE_PREFER_APPLETS
279 This option causes busybox shells to use busybox applets
280 in preference to executables in the PATH whenever possible. For
281 example, entering the command 'ifconfig' into the shell would cause
282 busybox to use the ifconfig busybox applet. Specifying the fully
283 qualified executable name, such as '/sbin/ifconfig' will still
284 execute the /sbin/ifconfig executable on the filesystem. This option
285 is generally used when creating a statically linked version of busybox
286 for use as a rescue shell, in the event that you screw up your system.
288 This is implemented by re-execing /proc/self/exe (typically)
289 with right parameters. Some selected applets ("NOFORK" applets)
290 can even be executed without creating new process.
291 Instead, busybox will call <applet>_main() internally.
293 However, this causes problems in chroot jails without mounted /proc
294 and with ps/top (command name can be shown as 'exe' for applets
297 # Note that this will *also* cause applets to take precedence
298 # over shell builtins of the same name. So turning this on will
299 # eliminate any performance gained by turning on the builtin "echo"
300 # and "test" commands in ash.
302 # Note that when using this option, the shell will attempt to directly
303 # run '/bin/busybox'. If you do not have the busybox binary sitting in
304 # that exact location with that exact name, this option will not work at
307 config FEATURE_SH_NOFORK
308 bool "Run 'nofork' applets directly"
310 depends on (MSH || LASH || HUSH || ASH) && FEATURE_PREFER_APPLETS
312 This option causes busybox shells [currently only ash]
313 to not execute typical fork/exec/wait sequence, but call <applet>_main
314 directly, if possible. (Sometimes it is not possible: for example,
315 this is not possible in pipes).
317 This will be done only for some applets (those which are marked
318 NOFORK in include/applets.h).
320 This may significantly speed up some shell scripts.
322 This feature is relatively new. Use with care.
328 One common problem reported on the mailing list is "can't access tty;
329 job control turned off" error message which typically appears when
330 one tries to use shell with stdin/stdout opened to /dev/console.
331 This device is special - it cannot be a controlling tty.
333 Proper solution is to use correct device instead of /dev/console.
335 cttyhack provides "quick and dirty" solution to this problem.
336 It analyzes stdin with various ioctls, trying to determine whether
337 it is a /dev/ttyN or /dev/ttySN (virtual terminal or serial line).
338 If it detects one, it closes stdin/out/err and reopens that device.
339 Then it executes given program. Usage example for /etc/inittab
342 ::respawn:/bin/cttyhack /bin/sh