2 # For a description of the syntax of this configuration file,
3 # see scripts/kbuild/config-language.txt.
6 mainmenu "BusyBox Configuration"
12 menu "Busybox Settings"
14 menu "General Configuration"
17 bool "Enable options for full-blown desktop systems"
20 Enable options and features which are not essential.
21 Select this only if you plan to use busybox on full-blown
22 desktop machine with common Linux distro, not on an embedded box.
25 bool "Provide compatible behavior for rare corner cases (bigger code)"
28 This option makes grep, sed etc handle rare corner cases
29 (embedded NUL bytes and such). This makes code bigger and uses
30 some GNU extensions in libc. You probably only need this option
31 if you plan to run busybox on desktop.
34 bool "Enable obsolete features removed before SUSv3"
37 This option will enable backwards compatibility with SuSv2,
38 specifically, old-style numeric options ('command -1 <file>')
39 will be supported in head, tail, and fold. (Note: should
42 config USE_PORTABLE_CODE
43 bool "Avoid using GCC-specific code constructs"
46 Use this option if you are trying to compile busybox with
47 compiler other than gcc.
48 If you do use gcc, this option may needlessly increase code size.
51 prompt "Buffer allocation policy"
52 default FEATURE_BUFFERS_USE_MALLOC
54 There are 3 ways BusyBox can handle buffer allocations:
55 - Use malloc. This costs code size for the call to xmalloc.
56 - Put them on stack. For some very small machines with limited stack
57 space, this can be deadly. For most folks, this works just fine.
58 - Put them in BSS. This works beautifully for computers with a real
59 MMU (and OS support), but wastes runtime RAM for uCLinux. This
60 behavior was the only one available for BusyBox versions 0.48 and
63 config FEATURE_BUFFERS_USE_MALLOC
64 bool "Allocate with Malloc"
66 config FEATURE_BUFFERS_GO_ON_STACK
67 bool "Allocate on the Stack"
69 config FEATURE_BUFFERS_GO_IN_BSS
70 bool "Allocate in the .bss section"
75 bool "Show terse applet usage messages"
78 All BusyBox applets will show help messages when invoked with
79 wrong arguments. You can turn off printing these terse usage
80 messages if you say no here.
81 This will save you up to 7k.
83 config FEATURE_VERBOSE_USAGE
84 bool "Show verbose applet usage messages"
88 All BusyBox applets will show more verbose help messages when
89 busybox is invoked with --help. This will add a lot of text to the
90 busybox binary. In the default configuration, this will add about
91 13k, but it can add much more depending on your configuration.
93 config FEATURE_COMPRESS_USAGE
94 bool "Store applet usage messages in compressed form"
98 Store usage messages in compressed form, uncompress them on-the-fly
99 when <applet> --help is called.
101 If you have a really tiny busybox with few applets enabled (and
102 bunzip2 isn't one of them), the overhead of the decompressor might
103 be noticeable. Also, if you run executables directly from ROM
104 and have very little memory, this might not be a win. Otherwise,
105 you probably want this.
107 config FEATURE_INSTALLER
108 bool "Support --install [-s] to install applet links at runtime"
111 Enable 'busybox --install [-s]' support. This will allow you to use
112 busybox at runtime to create hard links or symlinks for all the
113 applets that are compiled into busybox.
115 config LOCALE_SUPPORT
116 bool "Enable locale support (system needs locale for this to work)"
119 Enable this if your system has locale support and you would like
120 busybox to support locale settings.
122 config FEATURE_ASSUME_UNICODE
123 bool "Support Unicode"
126 This makes various applets aware that one byte is not
127 one character on screen.
129 Busybox aims to eventually work correctly with Unicode displays.
130 Any older encodings are not guaranteed to work.
131 Probably by the time when busybox will be fully Unicode-clean,
132 other encodings will be mainly of historic interest.
134 config FEATURE_CHECK_UNICODE_IN_ENV
135 bool "Check $LANG environment variable"
137 depends on FEATURE_ASSUME_UNICODE && !LOCALE_SUPPORT
139 With this option on, Unicode support is activated
140 only if LANG variable has the value of the form "xxxx.utf8"
142 Otherwise, Unicode support will be always enabled and active.
145 int "Character code to substitute unprintable characters with"
146 depends on FEATURE_ASSUME_UNICODE
149 Typical values are 63 for '?' (works with any output device),
150 30 for ASCII substitute control code,
151 65533 (0xfffd) for Unicode replacement character.
153 config LAST_SUPPORTED_WCHAR
154 int "Range of supported Unicode characters"
155 depends on FEATURE_ASSUME_UNICODE
158 Any character with Unicode value bigger than this is assumed
159 to be non-printable on output device. Many applets replace
160 such chars with substitution character.
162 The idea is that many valid printable Unicode chars are
163 nevertheless are not displayed correctly. Think about
164 combining charachers, double-wide hieroglyphs, obscure
165 characters in dozens of ancient scripts...
166 Many terminals, terminal emulators, xterms etc will fail
167 to handle them correctly. Choose the smallest value
168 which suits your needs.
172 767 (0x2ff) - there are no combining chars in [0..767] range
173 (the range includes Latin 1, Latin Ext. A and B),
174 code is ~700 bytes smaller for this case.
175 4351 (0x10ff) - there are no double-wide chars in [0..4351] range,
176 code is ~300 bytes smaller for this case.
177 12799 (0x31ff) - nearly all non-ideographic characters are
178 available in [0..12799] range, including
179 East Asian scripts like katakana, hiragana, hangul,
181 0 - off, any valid printable Unicode character will be printed.
183 config UNICODE_COMBINING_WCHARS
184 bool "Allow zero-width Unicode characters on output"
186 depends on FEATURE_ASSUME_UNICODE
188 With this option off, any Unicode char with width of 0
189 is substituted on output.
191 config UNICODE_WIDE_WCHARS
192 bool "Allow wide Unicode characters on output"
194 depends on FEATURE_ASSUME_UNICODE
196 With this option off, any Unicode char with width > 1
197 is substituted on output.
199 config UNICODE_BIDI_SUPPORT
200 bool "Bidirectional character-aware line input"
202 depends on FEATURE_ASSUME_UNICODE && !LOCALE_SUPPORT
204 With this option on, right-to-left Unicode characters
205 are treated differently on input (e.g. cursor movement).
207 config UNICODE_NEUTRAL_TABLE
208 bool "In bidi input, support non-ASCII neutral chars too"
210 depends on UNICODE_BIDI_SUPPORT
212 In most cases it's enough to treat only ASCII non-letters
213 (i.e. punctuation, numbers and space) as characters
214 with neutral directionality.
215 With this option on, more extensive (and bigger) table
216 of neutral chars will be used.
219 bool "Support for --long-options"
222 Enable this if you want busybox applets to use the gnu --long-option
223 style, in addition to single character -a -b -c style options.
225 config FEATURE_DEVPTS
226 bool "Use the devpts filesystem for Unix98 PTYs"
229 Enable if you want BusyBox to use Unix98 PTY support. If enabled,
230 busybox will use /dev/ptmx for the master side of the pseudoterminal
231 and /dev/pts/<number> for the slave side. Otherwise, BSD style
232 /dev/ttyp<number> will be used. To use this option, you should have
235 config FEATURE_CLEAN_UP
236 bool "Clean up all memory before exiting (usually not needed)"
239 As a size optimization, busybox normally exits without explicitly
240 freeing dynamically allocated memory or closing files. This saves
241 space since the OS will clean up for us, but it can confuse debuggers
242 like valgrind, which report tons of memory and resource leaks.
244 Don't enable this unless you have a really good reason to clean
247 config FEATURE_PIDFILE
248 bool "Support writing pidfiles"
251 This option makes some applets (e.g. crond, syslogd, inetd) write
252 a pidfile in /var/run. Some applications rely on them.
255 bool "Support for SUID/SGID handling"
258 With this option you can install the busybox binary belonging
259 to root with the suid bit set, and it will automatically drop
260 priviledges for applets that don't need root access.
262 If you are really paranoid and don't want to do this, build two
263 busybox binaries with different applets in them (and the appropriate
264 symlinks pointing to each binary), and only set the suid bit on the
265 one that needs it. The applets currently marked to need the suid bit
268 crontab, dnsd, findfs, ipcrm, ipcs, login, passwd, ping, su,
271 config FEATURE_SUID_CONFIG
272 bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
273 default n if FEATURE_SUID
274 depends on FEATURE_SUID
276 Allow the SUID / SGID state of an applet to be determined at runtime
277 by checking /etc/busybox.conf. (This is sort of a poor man's sudo.)
278 The format of this file is as follows:
280 <applet> = [Ssx-][Ssx-][x-] (<username>|<uid>).(<groupname>|<gid>)
282 An example might help:
285 su = ssx root.0 # applet su can be run by anyone and runs with
287 su = ssx # exactly the same
289 mount = sx- root.disk # applet mount can be run by root and members
290 # of group disk and runs with euid=0
292 cp = --- # disable applet cp for everyone
294 The file has to be owned by user root, group root and has to be
295 writeable only by root:
296 (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf)
297 The busybox executable has to be owned by user root, group
298 root and has to be setuid root for this to work:
299 (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox)
301 Robert 'sandman' Griebl has more information here:
302 <url: http://www.softforge.de/bb/suid.html >.
304 config FEATURE_SUID_CONFIG_QUIET
305 bool "Suppress warning message if /etc/busybox.conf is not readable"
307 depends on FEATURE_SUID_CONFIG
309 /etc/busybox.conf should be readable by the user needing the SUID,
310 check this option to avoid users to be notified about missing
314 bool "Support NSA Security Enhanced Linux"
317 Enable support for SELinux in applets ls, ps, and id. Also provide
318 the option of compiling in SELinux applets.
320 If you do not have a complete SELinux userland installed, this stuff
321 will not compile. Go visit
322 http://www.nsa.gov/selinux/index.html
323 to download the necessary stuff to allow busybox to compile with
324 this option enabled. Specifially, libselinux 1.28 or better is
325 directly required by busybox. If the installation is located in a
326 non-standard directory, provide it by invoking make as follows:
327 CFLAGS=-I<libselinux-include-path> \
328 LDFLAGS=-L<libselinux-lib-path> \
331 Most people will leave this set to 'N'.
333 config FEATURE_PREFER_APPLETS
334 bool "exec prefers applets"
337 This is an experimental option which directs applets about to
338 call 'exec' to try and find an applicable busybox applet before
339 searching the PATH. This is typically done by exec'ing
341 This may affect shell, find -exec, xargs and similar applets.
342 They will use applets even if /bin/<applet> -> busybox link
343 is missing (or is not a link to busybox). However, this causes
344 problems in chroot jails without mounted /proc and with ps/top
345 (command name can be shown as 'exe' for applets started this way).
347 config BUSYBOX_EXEC_PATH
348 string "Path to BusyBox executable"
349 default "/proc/self/exe"
351 When Busybox applets need to run other busybox applets, BusyBox
352 sometimes needs to exec() itself. When the /proc filesystem is
353 mounted, /proc/self/exe always points to the currently running
354 executable. If you haven't got /proc, set this to wherever you
355 want to run BusyBox from.
357 # These are auto-selected by other options
359 config FEATURE_SYSLOG
360 bool #No description makes it a hidden option
363 # This option is auto-selected when you select any applet which may
364 # send its output to syslog. You do not need to select it manually.
366 config FEATURE_HAVE_RPC
367 bool #No description makes it a hidden option
370 # This is automatically selected if any of enabled applets need it.
371 # You do not need to select it manually.
378 bool "Build BusyBox as a static binary (no shared libs)"
381 If you want to build a static BusyBox binary, which does not
382 use or require any shared libraries, then enable this option.
383 This can cause BusyBox to be considerably larger, so you should
384 leave this option false unless you have a good reason (i.e.
385 your target platform does not support shared libraries, or
386 you are building an initrd which doesn't need anything but
389 Most people will leave this set to 'N'.
392 bool "Build BusyBox as a position independent executable"
396 (TODO: what is it and why/when is it useful?)
397 Most people will leave this set to 'N'.
400 bool "Force NOMMU build"
403 Busybox tries to detect whether architecture it is being
404 built against supports MMU or not. If this detection fails,
405 or if you want to build NOMMU version of busybox for testing,
406 you may force NOMMU build here.
408 Most people will leave this set to 'N'.
410 # PIE can be made to work with BUILD_LIBBUSYBOX, but currently
411 # build system does not support that
412 config BUILD_LIBBUSYBOX
413 bool "Build shared libbusybox"
415 depends on !FEATURE_PREFER_APPLETS && !PIE && !STATIC
417 Build a shared library libbusybox.so.N.N.N which contains all
420 This feature allows every applet to be built as a tiny
421 separate executable. Enabling it for "one big busybox binary"
422 approach serves no purpose and increases code size.
423 You should almost certainly say "no" to this.
425 ### config FEATURE_FULL_LIBBUSYBOX
426 ### bool "Feature-complete libbusybox"
427 ### default n if !FEATURE_SHARED_BUSYBOX
428 ### depends on BUILD_LIBBUSYBOX
430 ### Build a libbusybox with the complete feature-set, disregarding
431 ### the actually selected config.
433 ### Normally, libbusybox will only contain the features which are
434 ### used by busybox itself. If you plan to write a separate
435 ### standalone application which uses libbusybox say 'Y'.
437 ### Note: libbusybox is GPL, not LGPL, and exports no stable API that
438 ### might act as a copyright barrier. We can and will modify the
439 ### exported function set between releases (even minor version number
440 ### changes), and happily break out-of-tree features.
442 ### Say 'N' if in doubt.
444 config FEATURE_INDIVIDUAL
445 bool "Produce a binary for each applet, linked against libbusybox"
447 depends on BUILD_LIBBUSYBOX
449 If your CPU architecture doesn't allow for sharing text/rodata
450 sections of running binaries, but allows for runtime dynamic
451 libraries, this option will allow you to reduce memory footprint
452 when you have many different applets running at once.
454 If your CPU architecture allows for sharing text/rodata,
455 having single binary is more optimal.
457 Each applet will be a tiny program, dynamically linked
458 against libbusybox.so.N.N.N.
460 You need to have a working dynamic linker.
462 config FEATURE_SHARED_BUSYBOX
463 bool "Produce additional busybox binary linked against libbusybox"
465 depends on BUILD_LIBBUSYBOX
467 Build busybox, dynamically linked against libbusybox.so.N.N.N.
469 You need to have a working dynamic linker.
471 ### config BUILD_AT_ONCE
472 ### bool "Compile all sources at once"
475 ### Normally each source-file is compiled with one invocation of
477 ### If you set this option, all sources are compiled at once.
478 ### This gives the compiler more opportunities to optimize which can
479 ### result in smaller and/or faster binaries.
481 ### Setting this option will consume alot of memory, e.g. if you
482 ### enable all applets with all features, gcc uses more than 300MB
483 ### RAM during compilation of busybox.
485 ### This option is most likely only beneficial for newer compilers
486 ### such as gcc-4.1 and above.
488 ### Say 'N' unless you know what you are doing.
491 bool "Build with Large File Support (for accessing files > 2 GB)"
493 select FDISK_SUPPORT_LARGE_DISKS
495 If you want to build BusyBox with large file support, then enable
496 this option. This will have no effect if your kernel or your C
497 library lacks large file support for large files. Some of the
498 programs that can benefit from large file support include dd, gzip,
499 cp, mount, tar, and many others. If you want to access files larger
500 than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'.
502 config CROSS_COMPILER_PREFIX
503 string "Cross Compiler prefix"
506 If you want to build BusyBox with a cross compiler, then you
507 will need to set this to the cross-compiler prefix, for example,
510 Note that CROSS_COMPILE environment variable or
511 "make CROSS_COMPILE=xxx ..." will override this selection.
513 Native builds leave this empty.
516 string "Additional CFLAGS"
519 Additional CFLAGS to pass to the compiler verbatim.
523 menu 'Debugging Options'
526 bool "Build BusyBox with extra Debugging symbols"
529 Say Y here if you wish to examine BusyBox internals while applets are
530 running. This increases the size of the binary considerably, and
531 should only be used when doing development. If you are doing
532 development and want to debug BusyBox, answer Y.
534 Most people should answer N.
536 config DEBUG_PESSIMIZE
537 bool "Disable compiler optimizations"
541 The compiler's optimization of source code can eliminate and reorder
542 code, resulting in an executable that's hard to understand when
543 stepping through it with a debugger. This switches it off, resulting
544 in a much bigger executable that more closely matches the source
548 bool "Abort compilation on any warning"
551 Selecting this will add -Werror to gcc command line.
553 Most people should answer N.
556 prompt "Additional debugging library"
559 Using an additional debugging library will make BusyBox become
560 considerable larger and will cause it to run more slowly. You
561 should always leave this option disabled for production use.
565 This enables compiling with dmalloc ( http://dmalloc.com/ )
566 which is an excellent public domain mem leak and malloc problem
567 detector. To enable dmalloc, before running busybox you will
568 want to properly set your environment, for example:
569 export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
570 The 'debug=' value is generated using the following command
571 dmalloc -p log-stats -p log-non-free -p log-bad-space \
572 -p log-elapsed-time -p check-fence -p check-heap \
573 -p check-lists -p check-blank -p check-funcs -p realloc-copy \
576 Electric-fence support:
577 -----------------------
578 This enables compiling with Electric-fence support. Electric
579 fence is another very useful malloc debugging library which uses
580 your computer's virtual memory hardware to detect illegal memory
581 accesses. This support will make BusyBox be considerable larger
582 and run slower, so you should leave this option disabled unless
583 you are hunting a hard to find memory problem.
593 bool "Electric-fence"
598 ### bool "Uniform config file parser debugging applet: parse"
602 menu 'Installation Options'
604 config INSTALL_NO_USR
605 bool "Don't use /usr"
608 Disable use of /usr. Don't activate this option if you don't know
609 that you really want this behaviour.
612 prompt "Applets links"
613 default INSTALL_APPLET_SYMLINKS
615 Choose how you install applets links.
617 config INSTALL_APPLET_SYMLINKS
620 Install applets as soft-links to the busybox binary. This needs some
621 free inodes on the filesystem, but might help with filesystem
622 generators that can't cope with hard-links.
624 config INSTALL_APPLET_HARDLINKS
627 Install applets as hard-links to the busybox binary. This might
628 count on a filesystem with few inodes.
630 config INSTALL_APPLET_SCRIPT_WRAPPERS
631 bool "as script wrappers"
633 Install applets as script wrappers that call the busybox binary.
635 config INSTALL_APPLET_DONT
637 depends on FEATURE_INSTALLER || FEATURE_SH_STANDALONE || FEATURE_PREFER_APPLETS
639 Do not install applet links. Useful when using the -install feature
640 or a standalone shell for rescue purposes.
645 prompt "/bin/sh applet link"
646 default INSTALL_SH_APPLET_SYMLINK
647 depends on INSTALL_APPLET_SCRIPT_WRAPPERS
649 Choose how you install /bin/sh applet link.
651 config INSTALL_SH_APPLET_SYMLINK
654 Install /bin/sh applet as soft-link to the busybox binary.
656 config INSTALL_SH_APPLET_HARDLINK
659 Install /bin/sh applet as hard-link to the busybox binary.
661 config INSTALL_SH_APPLET_SCRIPT_WRAPPER
662 bool "as script wrapper"
664 Install /bin/sh applet as script wrapper that call the busybox
670 string "BusyBox installation prefix"
673 Define your directory to install BusyBox files/subdirs in.
677 source libbb/Config.in
683 source archival/Config.in
684 source coreutils/Config.in
685 source console-tools/Config.in
686 source debianutils/Config.in
687 source editors/Config.in
688 source findutils/Config.in
689 source init/Config.in
690 source loginutils/Config.in
691 source e2fsprogs/Config.in
692 source modutils/Config.in
693 source util-linux/Config.in
694 source miscutils/Config.in
695 source networking/Config.in
696 source printutils/Config.in
697 source mailutils/Config.in
698 source procps/Config.in
699 source runit/Config.in
700 source selinux/Config.in
701 source shell/Config.in
702 source sysklogd/Config.in