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 prompt "Buffer allocation policy"
26 default FEATURE_BUFFERS_USE_MALLOC
28 There are 3 ways BusyBox can handle buffer allocations:
29 - Use malloc. This costs code size for the call to xmalloc.
30 - Put them on stack. For some very small machines with limited stack
31 space, this can be deadly. For most folks, this works just fine.
32 - Put them in BSS. This works beautifully for computers with a real
33 MMU (and OS support), but wastes runtime RAM for uCLinux. This
34 behavior was the only one available for BusyBox versions 0.48 and
37 config FEATURE_BUFFERS_USE_MALLOC
38 bool "Allocate with Malloc"
40 config FEATURE_BUFFERS_GO_ON_STACK
41 bool "Allocate on the Stack"
43 config FEATURE_BUFFERS_GO_IN_BSS
44 bool "Allocate in the .bss section"
49 bool "Show terse applet usage messages"
52 All BusyBox applets will show help messages when invoked with
53 wrong arguments. You can turn off printing these terse usage
54 messages if you say no here.
55 This will save you up to 7k.
57 config FEATURE_VERBOSE_USAGE
58 bool "Show verbose applet usage messages"
62 All BusyBox applets will show more verbose help messages when
63 busybox is invoked with --help. This will add a lot of text to the
64 busybox binary. In the default configuration, this will add about
65 13k, but it can add much more depending on your configuration.
67 config FEATURE_COMPRESS_USAGE
68 bool "Store applet usage messages in compressed form"
72 Store usage messages in compressed form, uncompress them on-the-fly
73 when <applet> --help is called.
75 If you have a really tiny busybox with few applets enabled (and
76 bunzip2 isn't one of them), the overhead of the decompressor might
77 be noticeable. Also, if you run executables directly from ROM
78 and have very little memory, this might not be a win. Otherwise,
79 you probably want this.
81 config FEATURE_INSTALLER
82 bool "Support --install [-s] to install applet links at runtime"
85 Enable 'busybox --install [-s]' support. This will allow you to use
86 busybox at runtime to create hard links or symlinks for all the
87 applets that are compiled into busybox.
90 bool "Enable locale support (system needs locale for this to work)"
93 Enable this if your system has locale support and you would like
94 busybox to support locale settings.
97 bool "Support for --long-options"
100 Enable this if you want busybox applets to use the gnu --long-option
101 style, in addition to single character -a -b -c style options.
103 config FEATURE_DEVPTS
104 bool "Use the devpts filesystem for Unix98 PTYs"
107 Enable if you want BusyBox to use Unix98 PTY support. If enabled,
108 busybox will use /dev/ptmx for the master side of the pseudoterminal
109 and /dev/pts/<number> for the slave side. Otherwise, BSD style
110 /dev/ttyp<number> will be used. To use this option, you should have
113 config FEATURE_CLEAN_UP
114 bool "Clean up all memory before exiting (usually not needed)"
117 As a size optimization, busybox normally exits without explicitly
118 freeing dynamically allocated memory or closing files. This saves
119 space since the OS will clean up for us, but it can confuse debuggers
120 like valgrind, which report tons of memory and resource leaks.
122 Don't enable this unless you have a really good reason to clean
125 config FEATURE_PIDFILE
126 bool "Support writing pidfiles"
129 This option makes some applets (e.g. crond, syslogd, inetd) write
130 a pidfile in /var/run. Some applications rely on them.
133 bool "Support for SUID/SGID handling"
136 With this option you can install the busybox binary belonging
137 to root with the suid bit set, and it'll and it'll automatically drop
138 priviledges for applets that don't need root access.
140 If you're really paranoid and don't want to do this, build two
141 busybox binaries with different applets in them (and the appropriate
142 symlinks pointing to each binary), and only set the suid bit on the
143 one that needs it. The applets currently marked to need the suid bit
144 are login, passwd, su, ping, traceroute, crontab, dnsd, ipcrm, ipcs,
147 config FEATURE_SUID_CONFIG
148 bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
149 default n if FEATURE_SUID
150 depends on FEATURE_SUID
152 Allow the SUID / SGID state of an applet to be determined at runtime
153 by checking /etc/busybox.conf. (This is sort of a poor man's sudo.)
154 The format of this file is as follows:
156 <applet> = [Ssx-][Ssx-][x-] (<username>|<uid>).(<groupname>|<gid>)
158 An example might help:
161 su = ssx root.0 # applet su can be run by anyone and runs with euid=0/egid=0
162 su = ssx # exactly the same
164 mount = sx- root.disk # applet mount can be run by root and members of group disk
165 # and runs with euid=0
167 cp = --- # disable applet cp for everyone
169 The file has to be owned by user root, group root and has to be
170 writeable only by root:
171 (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf)
172 The busybox executable has to be owned by user root, group
173 root and has to be setuid root for this to work:
174 (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox)
176 Robert 'sandman' Griebl has more information here:
177 <url: http://www.softforge.de/bb/suid.html >.
179 config FEATURE_SUID_CONFIG_QUIET
180 bool "Suppress warning message if /etc/busybox.conf is not readable"
182 depends on FEATURE_SUID_CONFIG
184 /etc/busybox.conf should be readable by the user needing the SUID, check
185 this option to avoid users to be notified about missing permissions.
188 bool "Support NSA Security Enhanced Linux"
191 Enable support for SELinux in applets ls, ps, and id. Also provide
192 the option of compiling in SELinux applets.
194 If you do not have a complete SELinux userland installed, this stuff
195 will not compile. Go visit
196 http://www.nsa.gov/selinux/index.html
197 to download the necessary stuff to allow busybox to compile with
198 this option enabled. Specifially, libselinux 1.28 or better is
199 directly required by busybox. If the installation is located in a
200 non-standard directory, provide it by invoking make as follows:
201 CFLAGS=-I<libselinux-include-path> \
202 LDFLAGS=-L<libselinux-lib-path> \
205 Most people will leave this set to 'N'.
207 config FEATURE_PREFER_APPLETS
208 bool "exec prefers applets"
211 This is an experimental option which directs applets about to
212 call 'exec' to try and find an applicable busybox applet before
213 searching the PATH. This is typically done by exec'ing
215 This may affect shell, find -exec, xargs and similar applets.
216 They will use applets even if /bin/<applet> -> busybox link
217 is missing (or is not a link to busybox). However, this causes
218 problems in chroot jails without mounted /proc and with ps/top
219 (command name can be shown as 'exe' for applets started this way).
221 config BUSYBOX_EXEC_PATH
222 string "Path to BusyBox executable"
223 default "/proc/self/exe"
225 When Busybox applets need to run other busybox applets, BusyBox
226 sometimes needs to exec() itself. When the /proc filesystem is
227 mounted, /proc/self/exe always points to the currently running
228 executable. If you haven't got /proc, set this to wherever you
229 want to run BusyBox from.
231 # These are auto-selected by other options
233 config FEATURE_SYSLOG
234 bool "Support for logging to syslog"
237 This option is auto-selected when you select any applet which may
238 send its output to syslog. You do not need to select it manually.
240 config FEATURE_HAVE_RPC
244 This is automatically selected if any of enabled applets need it.
245 You do not need to select it manually.
252 bool "Build BusyBox as a static binary (no shared libs)"
255 If you want to build a static BusyBox binary, which does not
256 use or require any shared libraries, then enable this option.
257 This can cause BusyBox to be considerably larger, so you should
258 leave this option false unless you have a good reason (i.e.
259 your target platform does not support shared libraries, or
260 you are building an initrd which doesn't need anything but
263 Most people will leave this set to 'N'.
266 bool "Build BusyBox as a position independent executable"
270 (TODO: what is it and why/when is it useful?)
271 Most people will leave this set to 'N'.
274 bool "Force NOMMU build"
277 Busybox tries to detect whether architecture it is being
278 built against supports MMU or not. If this detection fails,
279 or if you want to build NOMMU version of busybox for testing,
280 you may force NOMMU build here.
282 Most people will leave this set to 'N'.
284 config BUILD_LIBBUSYBOX
285 bool "Build shared libbusybox"
287 depends on !FEATURE_PREFER_APPLETS
289 Build a shared library libbusybox.so.N.N.N which contains all
292 This feature allows every applet to be built as a tiny
293 separate executable. Enabling it for "one big busybox binary"
294 approach serves no purpose and increases code size.
295 You should almost certainly say "no" to this.
297 ### config FEATURE_FULL_LIBBUSYBOX
298 ### bool "Feature-complete libbusybox"
299 ### default n if !FEATURE_SHARED_BUSYBOX
300 ### depends on BUILD_LIBBUSYBOX
302 ### Build a libbusybox with the complete feature-set, disregarding
303 ### the actually selected config.
305 ### Normally, libbusybox will only contain the features which are
306 ### used by busybox itself. If you plan to write a separate
307 ### standalone application which uses libbusybox say 'Y'.
309 ### Note: libbusybox is GPL, not LGPL, and exports no stable API that
310 ### might act as a copyright barrier. We can and will modify the
311 ### exported function set between releases (even minor version number
312 ### changes), and happily break out-of-tree features.
314 ### Say 'N' if in doubt.
316 config FEATURE_INDIVIDUAL
317 bool "Produce a binary for each applet, linked against libbusybox"
319 depends on !STATIC && BUILD_LIBBUSYBOX
321 If your CPU architecture doesn't allow for sharing text/rodata
322 sections of running binaries, but allows for runtime dynamic
323 libraries, this option will allow you to reduce memory footprint
324 when you have many different applets running at once.
326 If your CPU architecture allows for sharing text/rodata,
327 having single binary is more optimal.
329 Each applet will be a tiny program, dynamically linked
330 against libbusybox.so.N.N.N.
332 You need to have a working dynamic linker.
334 config FEATURE_SHARED_BUSYBOX
335 bool "Produce additional busybox binary linked against libbusybox"
337 depends on !STATIC && BUILD_LIBBUSYBOX
339 Build busybox, dynamically linked against libbusybox.so.N.N.N.
341 You need to have a working dynamic linker.
343 ### config BUILD_AT_ONCE
344 ### bool "Compile all sources at once"
347 ### Normally each source-file is compiled with one invocation of
349 ### If you set this option, all sources are compiled at once.
350 ### This gives the compiler more opportunities to optimize which can
351 ### result in smaller and/or faster binaries.
353 ### Setting this option will consume alot of memory, e.g. if you
354 ### enable all applets with all features, gcc uses more than 300MB
355 ### RAM during compilation of busybox.
357 ### This option is most likely only beneficial for newer compilers
358 ### such as gcc-4.1 and above.
360 ### Say 'N' unless you know what you are doing.
363 bool "Build with Large File Support (for accessing files > 2 GB)"
365 select FDISK_SUPPORT_LARGE_DISKS
367 If you want to build BusyBox with large file support, then enable
368 this option. This will have no effect if your kernel or your C
369 library lacks large file support for large files. Some of the
370 programs that can benefit from large file support include dd, gzip,
371 cp, mount, tar, and many others. If you want to access files larger
372 than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'.
374 config CROSS_COMPILER_PREFIX
375 string "Cross Compiler prefix"
378 If you want to build BusyBox with a cross compiler, then you
379 will need to set this to the cross-compiler prefix, for example,
380 "i386-uclibc-". Note that CROSS_COMPILE environment variable
381 or "make CROSS_COMPILE=xxx ..." will override this selection.
382 For native build leave it empty.
386 menu 'Debugging Options'
389 bool "Build BusyBox with extra Debugging symbols"
392 Say Y here if you wish to examine BusyBox internals while applets are
393 running. This increases the size of the binary considerably, and
394 should only be used when doing development. If you are doing
395 development and want to debug BusyBox, answer Y.
397 Most people should answer N.
399 config DEBUG_PESSIMIZE
400 bool "Disable compiler optimizations."
404 The compiler's optimization of source code can eliminate and reorder
405 code, resulting in an executable that's hard to understand when
406 stepping through it with a debugger. This switches it off, resulting
407 in a much bigger executable that more closely matches the source
411 bool "Abort compilation on any warning"
414 Selecting this will add -Werror to gcc command line.
416 Most people should answer N.
419 prompt "Additional debugging library"
422 Using an additional debugging library will make BusyBox become
423 considerable larger and will cause it to run more slowly. You
424 should always leave this option disabled for production use.
428 This enables compiling with dmalloc ( http://dmalloc.com/ )
429 which is an excellent public domain mem leak and malloc problem
430 detector. To enable dmalloc, before running busybox you will
431 want to properly set your environment, for example:
432 export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
433 The 'debug=' value is generated using the following command
434 dmalloc -p log-stats -p log-non-free -p log-bad-space -p log-elapsed-time \
435 -p check-fence -p check-heap -p check-lists -p check-blank \
436 -p check-funcs -p realloc-copy -p allow-free-null
438 Electric-fence support:
439 -----------------------
440 This enables compiling with Electric-fence support. Electric
441 fence is another very useful malloc debugging library which uses
442 your computer's virtual memory hardware to detect illegal memory
443 accesses. This support will make BusyBox be considerable larger
444 and run slower, so you should leave this option disabled unless
445 you are hunting a hard to find memory problem.
455 bool "Electric-fence"
460 bool "Enable obsolete features removed before SUSv3?"
463 This option will enable backwards compatibility with SuSv2,
464 specifically, old-style numeric options ('command -1 <file>')
465 will be supported in head, tail, and fold. (Note: should
470 menu 'Installation Options'
472 config INSTALL_NO_USR
473 bool "Don't use /usr"
476 Disable use of /usr. Don't activate this option if you don't know
477 that you really want this behaviour.
480 prompt "Applets links"
481 default INSTALL_APPLET_SYMLINKS
483 Choose how you install applets links.
485 config INSTALL_APPLET_SYMLINKS
488 Install applets as soft-links to the busybox binary. This needs some
489 free inodes on the filesystem, but might help with filesystem
490 generators that can't cope with hard-links.
492 config INSTALL_APPLET_HARDLINKS
495 Install applets as hard-links to the busybox binary. This might count
496 on a filesystem with few inodes.
498 config INSTALL_APPLET_SCRIPT_WRAPPERS
499 bool "as script wrappers"
501 Install applets as script wrappers that call the busybox binary.
503 config INSTALL_APPLET_DONT
505 depends on FEATURE_INSTALLER || FEATURE_SH_STANDALONE || FEATURE_PREFER_APPLETS
507 Do not install applet links. Useful when using the -install feature
508 or a standalone shell for rescue purposes.
513 prompt "/bin/sh applet link"
514 default INSTALL_SH_APPLET_SYMLINK
515 depends on INSTALL_APPLET_SCRIPT_WRAPPERS
517 Choose how you install /bin/sh applet link.
519 config INSTALL_SH_APPLET_SYMLINK
522 Install /bin/sh applet as soft-link to the busybox binary.
524 config INSTALL_SH_APPLET_HARDLINK
527 Install /bin/sh applet as hard-link to the busybox binary.
529 config INSTALL_SH_APPLET_SCRIPT_WRAPPER
530 bool "as script wrapper"
532 Install /bin/sh applet as script wrapper that call the busybox binary.
537 string "BusyBox installation prefix"
540 Define your directory to install BusyBox files/subdirs in.
544 source libbb/Config.in
550 source archival/Config.in
551 source coreutils/Config.in
552 source console-tools/Config.in
553 source debianutils/Config.in
554 source editors/Config.in
555 source findutils/Config.in
556 source init/Config.in
557 source loginutils/Config.in
558 source e2fsprogs/Config.in
559 source modutils/Config.in
560 source util-linux/Config.in
561 source miscutils/Config.in
562 source networking/Config.in
563 source procps/Config.in
564 source shell/Config.in
565 source sysklogd/Config.in
566 source runit/Config.in
567 source selinux/Config.in
568 source printutils/Config.in