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.
33 config USE_PORTABLE_CODE
34 bool "Avoid using GCC-specific code constructs"
37 Use this option if you are trying to compile busybox with
38 compiler other than gcc.
39 If you do use gcc, this option may needlessly increase code size.
42 prompt "Buffer allocation policy"
43 default FEATURE_BUFFERS_USE_MALLOC
45 There are 3 ways BusyBox can handle buffer allocations:
46 - Use malloc. This costs code size for the call to xmalloc.
47 - Put them on stack. For some very small machines with limited stack
48 space, this can be deadly. For most folks, this works just fine.
49 - Put them in BSS. This works beautifully for computers with a real
50 MMU (and OS support), but wastes runtime RAM for uCLinux. This
51 behavior was the only one available for BusyBox versions 0.48 and
54 config FEATURE_BUFFERS_USE_MALLOC
55 bool "Allocate with Malloc"
57 config FEATURE_BUFFERS_GO_ON_STACK
58 bool "Allocate on the Stack"
60 config FEATURE_BUFFERS_GO_IN_BSS
61 bool "Allocate in the .bss section"
66 bool "Show terse applet usage messages"
69 All BusyBox applets will show help messages when invoked with
70 wrong arguments. You can turn off printing these terse usage
71 messages if you say no here.
72 This will save you up to 7k.
74 config FEATURE_VERBOSE_USAGE
75 bool "Show verbose applet usage messages"
79 All BusyBox applets will show more verbose help messages when
80 busybox is invoked with --help. This will add a lot of text to the
81 busybox binary. In the default configuration, this will add about
82 13k, but it can add much more depending on your configuration.
84 config FEATURE_COMPRESS_USAGE
85 bool "Store applet usage messages in compressed form"
89 Store usage messages in compressed form, uncompress them on-the-fly
90 when <applet> --help is called.
92 If you have a really tiny busybox with few applets enabled (and
93 bunzip2 isn't one of them), the overhead of the decompressor might
94 be noticeable. Also, if you run executables directly from ROM
95 and have very little memory, this might not be a win. Otherwise,
96 you probably want this.
98 config FEATURE_INSTALLER
99 bool "Support --install [-s] to install applet links at runtime"
102 Enable 'busybox --install [-s]' support. This will allow you to use
103 busybox at runtime to create hard links or symlinks for all the
104 applets that are compiled into busybox.
106 config LOCALE_SUPPORT
107 bool "Enable locale support (system needs locale for this to work)"
110 Enable this if your system has locale support and you would like
111 busybox to support locale settings.
113 config FEATURE_ASSUME_UNICODE
114 bool "Support Unicode"
117 This makes various applets aware that one byte is not
118 one character on screen.
120 Busybox aims to eventually work correctly with Unicode displays.
121 Any older encodings are not guaranteed to work.
122 Probably by the time when busybox will be fully Unicode-clean,
123 other encodings will be mainly of historic interest.
125 config FEATURE_CHECK_UNICODE_IN_ENV
126 bool "Check $LANG environment variable"
128 depends on FEATURE_ASSUME_UNICODE && !LOCALE_SUPPORT
130 With this option on, Unicode support is activated
131 only if LANG variable has the value of the form "xxxx.utf8"
133 Otherwise, Unicode support will be always enabled and active.
136 bool "Support for --long-options"
139 Enable this if you want busybox applets to use the gnu --long-option
140 style, in addition to single character -a -b -c style options.
142 config FEATURE_DEVPTS
143 bool "Use the devpts filesystem for Unix98 PTYs"
146 Enable if you want BusyBox to use Unix98 PTY support. If enabled,
147 busybox will use /dev/ptmx for the master side of the pseudoterminal
148 and /dev/pts/<number> for the slave side. Otherwise, BSD style
149 /dev/ttyp<number> will be used. To use this option, you should have
152 config FEATURE_CLEAN_UP
153 bool "Clean up all memory before exiting (usually not needed)"
156 As a size optimization, busybox normally exits without explicitly
157 freeing dynamically allocated memory or closing files. This saves
158 space since the OS will clean up for us, but it can confuse debuggers
159 like valgrind, which report tons of memory and resource leaks.
161 Don't enable this unless you have a really good reason to clean
164 config FEATURE_PIDFILE
165 bool "Support writing pidfiles"
168 This option makes some applets (e.g. crond, syslogd, inetd) write
169 a pidfile in /var/run. Some applications rely on them.
172 bool "Support for SUID/SGID handling"
175 With this option you can install the busybox binary belonging
176 to root with the suid bit set, and it will automatically drop
177 priviledges for applets that don't need root access.
179 If you are really paranoid and don't want to do this, build two
180 busybox binaries with different applets in them (and the appropriate
181 symlinks pointing to each binary), and only set the suid bit on the
182 one that needs it. The applets currently marked to need the suid bit
185 crontab, dnsd, findfs, ipcrm, ipcs, login, passwd, ping, su,
188 config FEATURE_SUID_CONFIG
189 bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
190 default n if FEATURE_SUID
191 depends on FEATURE_SUID
193 Allow the SUID / SGID state of an applet to be determined at runtime
194 by checking /etc/busybox.conf. (This is sort of a poor man's sudo.)
195 The format of this file is as follows:
197 <applet> = [Ssx-][Ssx-][x-] (<username>|<uid>).(<groupname>|<gid>)
199 An example might help:
202 su = ssx root.0 # applet su can be run by anyone and runs with
204 su = ssx # exactly the same
206 mount = sx- root.disk # applet mount can be run by root and members
207 # of group disk and runs with euid=0
209 cp = --- # disable applet cp for everyone
211 The file has to be owned by user root, group root and has to be
212 writeable only by root:
213 (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf)
214 The busybox executable has to be owned by user root, group
215 root and has to be setuid root for this to work:
216 (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox)
218 Robert 'sandman' Griebl has more information here:
219 <url: http://www.softforge.de/bb/suid.html >.
221 config FEATURE_SUID_CONFIG_QUIET
222 bool "Suppress warning message if /etc/busybox.conf is not readable"
224 depends on FEATURE_SUID_CONFIG
226 /etc/busybox.conf should be readable by the user needing the SUID,
227 check this option to avoid users to be notified about missing
231 bool "Support NSA Security Enhanced Linux"
234 Enable support for SELinux in applets ls, ps, and id. Also provide
235 the option of compiling in SELinux applets.
237 If you do not have a complete SELinux userland installed, this stuff
238 will not compile. Go visit
239 http://www.nsa.gov/selinux/index.html
240 to download the necessary stuff to allow busybox to compile with
241 this option enabled. Specifially, libselinux 1.28 or better is
242 directly required by busybox. If the installation is located in a
243 non-standard directory, provide it by invoking make as follows:
244 CFLAGS=-I<libselinux-include-path> \
245 LDFLAGS=-L<libselinux-lib-path> \
248 Most people will leave this set to 'N'.
250 config FEATURE_PREFER_APPLETS
251 bool "exec prefers applets"
254 This is an experimental option which directs applets about to
255 call 'exec' to try and find an applicable busybox applet before
256 searching the PATH. This is typically done by exec'ing
258 This may affect shell, find -exec, xargs and similar applets.
259 They will use applets even if /bin/<applet> -> busybox link
260 is missing (or is not a link to busybox). However, this causes
261 problems in chroot jails without mounted /proc and with ps/top
262 (command name can be shown as 'exe' for applets started this way).
264 config BUSYBOX_EXEC_PATH
265 string "Path to BusyBox executable"
266 default "/proc/self/exe"
268 When Busybox applets need to run other busybox applets, BusyBox
269 sometimes needs to exec() itself. When the /proc filesystem is
270 mounted, /proc/self/exe always points to the currently running
271 executable. If you haven't got /proc, set this to wherever you
272 want to run BusyBox from.
274 # These are auto-selected by other options
276 config FEATURE_SYSLOG
277 bool #No description makes it a hidden option
280 # This option is auto-selected when you select any applet which may
281 # send its output to syslog. You do not need to select it manually.
283 config FEATURE_HAVE_RPC
284 bool #No description makes it a hidden option
287 # This is automatically selected if any of enabled applets need it.
288 # You do not need to select it manually.
295 bool "Build BusyBox as a static binary (no shared libs)"
298 If you want to build a static BusyBox binary, which does not
299 use or require any shared libraries, then enable this option.
300 This can cause BusyBox to be considerably larger, so you should
301 leave this option false unless you have a good reason (i.e.
302 your target platform does not support shared libraries, or
303 you are building an initrd which doesn't need anything but
306 Most people will leave this set to 'N'.
309 bool "Build BusyBox as a position independent executable"
313 (TODO: what is it and why/when is it useful?)
314 Most people will leave this set to 'N'.
317 bool "Force NOMMU build"
320 Busybox tries to detect whether architecture it is being
321 built against supports MMU or not. If this detection fails,
322 or if you want to build NOMMU version of busybox for testing,
323 you may force NOMMU build here.
325 Most people will leave this set to 'N'.
327 # PIE can be made to work with BUILD_LIBBUSYBOX, but currently
328 # build system does not support that
329 config BUILD_LIBBUSYBOX
330 bool "Build shared libbusybox"
332 depends on !FEATURE_PREFER_APPLETS && !PIE && !STATIC
334 Build a shared library libbusybox.so.N.N.N which contains all
337 This feature allows every applet to be built as a tiny
338 separate executable. Enabling it for "one big busybox binary"
339 approach serves no purpose and increases code size.
340 You should almost certainly say "no" to this.
342 ### config FEATURE_FULL_LIBBUSYBOX
343 ### bool "Feature-complete libbusybox"
344 ### default n if !FEATURE_SHARED_BUSYBOX
345 ### depends on BUILD_LIBBUSYBOX
347 ### Build a libbusybox with the complete feature-set, disregarding
348 ### the actually selected config.
350 ### Normally, libbusybox will only contain the features which are
351 ### used by busybox itself. If you plan to write a separate
352 ### standalone application which uses libbusybox say 'Y'.
354 ### Note: libbusybox is GPL, not LGPL, and exports no stable API that
355 ### might act as a copyright barrier. We can and will modify the
356 ### exported function set between releases (even minor version number
357 ### changes), and happily break out-of-tree features.
359 ### Say 'N' if in doubt.
361 config FEATURE_INDIVIDUAL
362 bool "Produce a binary for each applet, linked against libbusybox"
364 depends on BUILD_LIBBUSYBOX
366 If your CPU architecture doesn't allow for sharing text/rodata
367 sections of running binaries, but allows for runtime dynamic
368 libraries, this option will allow you to reduce memory footprint
369 when you have many different applets running at once.
371 If your CPU architecture allows for sharing text/rodata,
372 having single binary is more optimal.
374 Each applet will be a tiny program, dynamically linked
375 against libbusybox.so.N.N.N.
377 You need to have a working dynamic linker.
379 config FEATURE_SHARED_BUSYBOX
380 bool "Produce additional busybox binary linked against libbusybox"
382 depends on BUILD_LIBBUSYBOX
384 Build busybox, dynamically linked against libbusybox.so.N.N.N.
386 You need to have a working dynamic linker.
388 ### config BUILD_AT_ONCE
389 ### bool "Compile all sources at once"
392 ### Normally each source-file is compiled with one invocation of
394 ### If you set this option, all sources are compiled at once.
395 ### This gives the compiler more opportunities to optimize which can
396 ### result in smaller and/or faster binaries.
398 ### Setting this option will consume alot of memory, e.g. if you
399 ### enable all applets with all features, gcc uses more than 300MB
400 ### RAM during compilation of busybox.
402 ### This option is most likely only beneficial for newer compilers
403 ### such as gcc-4.1 and above.
405 ### Say 'N' unless you know what you are doing.
408 bool "Build with Large File Support (for accessing files > 2 GB)"
410 select FDISK_SUPPORT_LARGE_DISKS
412 If you want to build BusyBox with large file support, then enable
413 this option. This will have no effect if your kernel or your C
414 library lacks large file support for large files. Some of the
415 programs that can benefit from large file support include dd, gzip,
416 cp, mount, tar, and many others. If you want to access files larger
417 than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'.
419 config CROSS_COMPILER_PREFIX
420 string "Cross Compiler prefix"
423 If you want to build BusyBox with a cross compiler, then you
424 will need to set this to the cross-compiler prefix, for example,
427 Note that CROSS_COMPILE environment variable or
428 "make CROSS_COMPILE=xxx ..." will override this selection.
430 Native builds leave this empty.
433 string "Additional CFLAGS"
436 Additional CFLAGS to pass to the compiler verbatim.
440 menu 'Debugging Options'
443 bool "Build BusyBox with extra Debugging symbols"
446 Say Y here if you wish to examine BusyBox internals while applets are
447 running. This increases the size of the binary considerably, and
448 should only be used when doing development. If you are doing
449 development and want to debug BusyBox, answer Y.
451 Most people should answer N.
453 config DEBUG_PESSIMIZE
454 bool "Disable compiler optimizations"
458 The compiler's optimization of source code can eliminate and reorder
459 code, resulting in an executable that's hard to understand when
460 stepping through it with a debugger. This switches it off, resulting
461 in a much bigger executable that more closely matches the source
465 bool "Abort compilation on any warning"
468 Selecting this will add -Werror to gcc command line.
470 Most people should answer N.
473 prompt "Additional debugging library"
476 Using an additional debugging library will make BusyBox become
477 considerable larger and will cause it to run more slowly. You
478 should always leave this option disabled for production use.
482 This enables compiling with dmalloc ( http://dmalloc.com/ )
483 which is an excellent public domain mem leak and malloc problem
484 detector. To enable dmalloc, before running busybox you will
485 want to properly set your environment, for example:
486 export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
487 The 'debug=' value is generated using the following command
488 dmalloc -p log-stats -p log-non-free -p log-bad-space \
489 -p log-elapsed-time -p check-fence -p check-heap \
490 -p check-lists -p check-blank -p check-funcs -p realloc-copy \
493 Electric-fence support:
494 -----------------------
495 This enables compiling with Electric-fence support. Electric
496 fence is another very useful malloc debugging library which uses
497 your computer's virtual memory hardware to detect illegal memory
498 accesses. This support will make BusyBox be considerable larger
499 and run slower, so you should leave this option disabled unless
500 you are hunting a hard to find memory problem.
510 bool "Electric-fence"
515 bool "Enable obsolete features removed before SUSv3?"
518 This option will enable backwards compatibility with SuSv2,
519 specifically, old-style numeric options ('command -1 <file>')
520 will be supported in head, tail, and fold. (Note: should
524 ### bool "Uniform config file parser debugging applet: parse"
528 menu 'Installation Options'
530 config INSTALL_NO_USR
531 bool "Don't use /usr"
534 Disable use of /usr. Don't activate this option if you don't know
535 that you really want this behaviour.
538 prompt "Applets links"
539 default INSTALL_APPLET_SYMLINKS
541 Choose how you install applets links.
543 config INSTALL_APPLET_SYMLINKS
546 Install applets as soft-links to the busybox binary. This needs some
547 free inodes on the filesystem, but might help with filesystem
548 generators that can't cope with hard-links.
550 config INSTALL_APPLET_HARDLINKS
553 Install applets as hard-links to the busybox binary. This might
554 count on a filesystem with few inodes.
556 config INSTALL_APPLET_SCRIPT_WRAPPERS
557 bool "as script wrappers"
559 Install applets as script wrappers that call the busybox binary.
561 config INSTALL_APPLET_DONT
563 depends on FEATURE_INSTALLER || FEATURE_SH_STANDALONE || FEATURE_PREFER_APPLETS
565 Do not install applet links. Useful when using the -install feature
566 or a standalone shell for rescue purposes.
571 prompt "/bin/sh applet link"
572 default INSTALL_SH_APPLET_SYMLINK
573 depends on INSTALL_APPLET_SCRIPT_WRAPPERS
575 Choose how you install /bin/sh applet link.
577 config INSTALL_SH_APPLET_SYMLINK
580 Install /bin/sh applet as soft-link to the busybox binary.
582 config INSTALL_SH_APPLET_HARDLINK
585 Install /bin/sh applet as hard-link to the busybox binary.
587 config INSTALL_SH_APPLET_SCRIPT_WRAPPER
588 bool "as script wrapper"
590 Install /bin/sh applet as script wrapper that call the busybox
596 string "BusyBox installation prefix"
599 Define your directory to install BusyBox files/subdirs in.
603 source libbb/Config.in
609 source archival/Config.in
610 source coreutils/Config.in
611 source console-tools/Config.in
612 source debianutils/Config.in
613 source editors/Config.in
614 source findutils/Config.in
615 source init/Config.in
616 source loginutils/Config.in
617 source e2fsprogs/Config.in
618 source modutils/Config.in
619 source util-linux/Config.in
620 source miscutils/Config.in
621 source networking/Config.in
622 source printutils/Config.in
623 source mailutils/Config.in
624 source procps/Config.in
625 source runit/Config.in
626 source selinux/Config.in
627 source shell/Config.in
628 source sysklogd/Config.in