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.
24 config FEATURE_ASSUME_UNICODE
25 bool "Assume that 1:1 char/glyph correspondence is not true"
28 This makes various applets aware that one byte is not
29 one character on screen.
31 Busybox aims to eventually work correctly with Unicode displays.
32 Any older encodings are not guaranteed to work.
33 Probably by the time when busybox will be fully Unicode-clean,
34 other encodings will be mainly of historic interest.
37 prompt "Buffer allocation policy"
38 default FEATURE_BUFFERS_USE_MALLOC
40 There are 3 ways BusyBox can handle buffer allocations:
41 - Use malloc. This costs code size for the call to xmalloc.
42 - Put them on stack. For some very small machines with limited stack
43 space, this can be deadly. For most folks, this works just fine.
44 - Put them in BSS. This works beautifully for computers with a real
45 MMU (and OS support), but wastes runtime RAM for uCLinux. This
46 behavior was the only one available for BusyBox versions 0.48 and
49 config FEATURE_BUFFERS_USE_MALLOC
50 bool "Allocate with Malloc"
52 config FEATURE_BUFFERS_GO_ON_STACK
53 bool "Allocate on the Stack"
55 config FEATURE_BUFFERS_GO_IN_BSS
56 bool "Allocate in the .bss section"
61 bool "Show terse applet usage messages"
64 All BusyBox applets will show help messages when invoked with
65 wrong arguments. You can turn off printing these terse usage
66 messages if you say no here.
67 This will save you up to 7k.
69 config FEATURE_VERBOSE_USAGE
70 bool "Show verbose applet usage messages"
74 All BusyBox applets will show more verbose help messages when
75 busybox is invoked with --help. This will add a lot of text to the
76 busybox binary. In the default configuration, this will add about
77 13k, but it can add much more depending on your configuration.
79 config FEATURE_COMPRESS_USAGE
80 bool "Store applet usage messages in compressed form"
84 Store usage messages in compressed form, uncompress them on-the-fly
85 when <applet> --help is called.
87 If you have a really tiny busybox with few applets enabled (and
88 bunzip2 isn't one of them), the overhead of the decompressor might
89 be noticeable. Also, if you run executables directly from ROM
90 and have very little memory, this might not be a win. Otherwise,
91 you probably want this.
93 config FEATURE_INSTALLER
94 bool "Support --install [-s] to install applet links at runtime"
97 Enable 'busybox --install [-s]' support. This will allow you to use
98 busybox at runtime to create hard links or symlinks for all the
99 applets that are compiled into busybox.
101 config LOCALE_SUPPORT
102 bool "Enable locale support (system needs locale for this to work)"
105 Enable this if your system has locale support and you would like
106 busybox to support locale settings.
109 bool "Support for --long-options"
112 Enable this if you want busybox applets to use the gnu --long-option
113 style, in addition to single character -a -b -c style options.
115 config FEATURE_DEVPTS
116 bool "Use the devpts filesystem for Unix98 PTYs"
119 Enable if you want BusyBox to use Unix98 PTY support. If enabled,
120 busybox will use /dev/ptmx for the master side of the pseudoterminal
121 and /dev/pts/<number> for the slave side. Otherwise, BSD style
122 /dev/ttyp<number> will be used. To use this option, you should have
125 config FEATURE_CLEAN_UP
126 bool "Clean up all memory before exiting (usually not needed)"
129 As a size optimization, busybox normally exits without explicitly
130 freeing dynamically allocated memory or closing files. This saves
131 space since the OS will clean up for us, but it can confuse debuggers
132 like valgrind, which report tons of memory and resource leaks.
134 Don't enable this unless you have a really good reason to clean
137 config FEATURE_PIDFILE
138 bool "Support writing pidfiles"
141 This option makes some applets (e.g. crond, syslogd, inetd) write
142 a pidfile in /var/run. Some applications rely on them.
145 bool "Support for SUID/SGID handling"
148 With this option you can install the busybox binary belonging
149 to root with the suid bit set, and it'll and it'll automatically drop
150 priviledges for applets that don't need root access.
152 If you're really paranoid and don't want to do this, build two
153 busybox binaries with different applets in them (and the appropriate
154 symlinks pointing to each binary), and only set the suid bit on the
155 one that needs it. The applets currently marked to need the suid bit
156 are login, passwd, su, ping, traceroute, crontab, dnsd, ipcrm, ipcs,
159 config FEATURE_SUID_CONFIG
160 bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
161 default n if FEATURE_SUID
162 depends on FEATURE_SUID
164 Allow the SUID / SGID state of an applet to be determined at runtime
165 by checking /etc/busybox.conf. (This is sort of a poor man's sudo.)
166 The format of this file is as follows:
168 <applet> = [Ssx-][Ssx-][x-] (<username>|<uid>).(<groupname>|<gid>)
170 An example might help:
173 su = ssx root.0 # applet su can be run by anyone and runs with euid=0/egid=0
174 su = ssx # exactly the same
176 mount = sx- root.disk # applet mount can be run by root and members of group disk
177 # and runs with euid=0
179 cp = --- # disable applet cp for everyone
181 The file has to be owned by user root, group root and has to be
182 writeable only by root:
183 (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf)
184 The busybox executable has to be owned by user root, group
185 root and has to be setuid root for this to work:
186 (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox)
188 Robert 'sandman' Griebl has more information here:
189 <url: http://www.softforge.de/bb/suid.html >.
191 config FEATURE_SUID_CONFIG_QUIET
192 bool "Suppress warning message if /etc/busybox.conf is not readable"
194 depends on FEATURE_SUID_CONFIG
196 /etc/busybox.conf should be readable by the user needing the SUID, check
197 this option to avoid users to be notified about missing permissions.
200 bool "Support NSA Security Enhanced Linux"
203 Enable support for SELinux in applets ls, ps, and id. Also provide
204 the option of compiling in SELinux applets.
206 If you do not have a complete SELinux userland installed, this stuff
207 will not compile. Go visit
208 http://www.nsa.gov/selinux/index.html
209 to download the necessary stuff to allow busybox to compile with
210 this option enabled. Specifially, libselinux 1.28 or better is
211 directly required by busybox. If the installation is located in a
212 non-standard directory, provide it by invoking make as follows:
213 CFLAGS=-I<libselinux-include-path> \
214 LDFLAGS=-L<libselinux-lib-path> \
217 Most people will leave this set to 'N'.
219 config FEATURE_PREFER_APPLETS
220 bool "exec prefers applets"
223 This is an experimental option which directs applets about to
224 call 'exec' to try and find an applicable busybox applet before
225 searching the PATH. This is typically done by exec'ing
227 This may affect shell, find -exec, xargs and similar applets.
228 They will use applets even if /bin/<applet> -> busybox link
229 is missing (or is not a link to busybox). However, this causes
230 problems in chroot jails without mounted /proc and with ps/top
231 (command name can be shown as 'exe' for applets started this way).
233 config BUSYBOX_EXEC_PATH
234 string "Path to BusyBox executable"
235 default "/proc/self/exe"
237 When Busybox applets need to run other busybox applets, BusyBox
238 sometimes needs to exec() itself. When the /proc filesystem is
239 mounted, /proc/self/exe always points to the currently running
240 executable. If you haven't got /proc, set this to wherever you
241 want to run BusyBox from.
243 # These are auto-selected by other options
245 config FEATURE_SYSLOG
246 bool "Support for logging to syslog"
249 This option is auto-selected when you select any applet which may
250 send its output to syslog. You do not need to select it manually.
252 config FEATURE_HAVE_RPC
256 This is automatically selected if any of enabled applets need it.
257 You do not need to select it manually.
264 bool "Build BusyBox as a static binary (no shared libs)"
267 If you want to build a static BusyBox binary, which does not
268 use or require any shared libraries, then enable this option.
269 This can cause BusyBox to be considerably larger, so you should
270 leave this option false unless you have a good reason (i.e.
271 your target platform does not support shared libraries, or
272 you are building an initrd which doesn't need anything but
275 Most people will leave this set to 'N'.
278 bool "Build BusyBox as a position independent executable"
282 (TODO: what is it and why/when is it useful?)
283 Most people will leave this set to 'N'.
286 bool "Force NOMMU build"
289 Busybox tries to detect whether architecture it is being
290 built against supports MMU or not. If this detection fails,
291 or if you want to build NOMMU version of busybox for testing,
292 you may force NOMMU build here.
294 Most people will leave this set to 'N'.
296 # PIE can be made to work with BUILD_LIBBUSYBOX, but currently
297 # build system does not support that
298 config BUILD_LIBBUSYBOX
299 bool "Build shared libbusybox"
301 depends on !FEATURE_PREFER_APPLETS && !PIE
303 Build a shared library libbusybox.so.N.N.N which contains all
306 This feature allows every applet to be built as a tiny
307 separate executable. Enabling it for "one big busybox binary"
308 approach serves no purpose and increases code size.
309 You should almost certainly say "no" to this.
311 ### config FEATURE_FULL_LIBBUSYBOX
312 ### bool "Feature-complete libbusybox"
313 ### default n if !FEATURE_SHARED_BUSYBOX
314 ### depends on BUILD_LIBBUSYBOX
316 ### Build a libbusybox with the complete feature-set, disregarding
317 ### the actually selected config.
319 ### Normally, libbusybox will only contain the features which are
320 ### used by busybox itself. If you plan to write a separate
321 ### standalone application which uses libbusybox say 'Y'.
323 ### Note: libbusybox is GPL, not LGPL, and exports no stable API that
324 ### might act as a copyright barrier. We can and will modify the
325 ### exported function set between releases (even minor version number
326 ### changes), and happily break out-of-tree features.
328 ### Say 'N' if in doubt.
330 config FEATURE_INDIVIDUAL
331 bool "Produce a binary for each applet, linked against libbusybox"
333 depends on !STATIC && BUILD_LIBBUSYBOX
335 If your CPU architecture doesn't allow for sharing text/rodata
336 sections of running binaries, but allows for runtime dynamic
337 libraries, this option will allow you to reduce memory footprint
338 when you have many different applets running at once.
340 If your CPU architecture allows for sharing text/rodata,
341 having single binary is more optimal.
343 Each applet will be a tiny program, dynamically linked
344 against libbusybox.so.N.N.N.
346 You need to have a working dynamic linker.
348 config FEATURE_SHARED_BUSYBOX
349 bool "Produce additional busybox binary linked against libbusybox"
351 depends on !STATIC && BUILD_LIBBUSYBOX
353 Build busybox, dynamically linked against libbusybox.so.N.N.N.
355 You need to have a working dynamic linker.
357 ### config BUILD_AT_ONCE
358 ### bool "Compile all sources at once"
361 ### Normally each source-file is compiled with one invocation of
363 ### If you set this option, all sources are compiled at once.
364 ### This gives the compiler more opportunities to optimize which can
365 ### result in smaller and/or faster binaries.
367 ### Setting this option will consume alot of memory, e.g. if you
368 ### enable all applets with all features, gcc uses more than 300MB
369 ### RAM during compilation of busybox.
371 ### This option is most likely only beneficial for newer compilers
372 ### such as gcc-4.1 and above.
374 ### Say 'N' unless you know what you are doing.
377 bool "Build with Large File Support (for accessing files > 2 GB)"
379 select FDISK_SUPPORT_LARGE_DISKS
381 If you want to build BusyBox with large file support, then enable
382 this option. This will have no effect if your kernel or your C
383 library lacks large file support for large files. Some of the
384 programs that can benefit from large file support include dd, gzip,
385 cp, mount, tar, and many others. If you want to access files larger
386 than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'.
388 config CROSS_COMPILER_PREFIX
389 string "Cross Compiler prefix"
392 If you want to build BusyBox with a cross compiler, then you
393 will need to set this to the cross-compiler prefix, for example,
394 "i386-uclibc-". Note that CROSS_COMPILE environment variable
395 or "make CROSS_COMPILE=xxx ..." will override this selection.
396 For native build leave it empty.
400 menu 'Debugging Options'
403 bool "Build BusyBox with extra Debugging symbols"
406 Say Y here if you wish to examine BusyBox internals while applets are
407 running. This increases the size of the binary considerably, and
408 should only be used when doing development. If you are doing
409 development and want to debug BusyBox, answer Y.
411 Most people should answer N.
413 config DEBUG_PESSIMIZE
414 bool "Disable compiler optimizations."
418 The compiler's optimization of source code can eliminate and reorder
419 code, resulting in an executable that's hard to understand when
420 stepping through it with a debugger. This switches it off, resulting
421 in a much bigger executable that more closely matches the source
425 bool "Abort compilation on any warning"
428 Selecting this will add -Werror to gcc command line.
430 Most people should answer N.
433 prompt "Additional debugging library"
436 Using an additional debugging library will make BusyBox become
437 considerable larger and will cause it to run more slowly. You
438 should always leave this option disabled for production use.
442 This enables compiling with dmalloc ( http://dmalloc.com/ )
443 which is an excellent public domain mem leak and malloc problem
444 detector. To enable dmalloc, before running busybox you will
445 want to properly set your environment, for example:
446 export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
447 The 'debug=' value is generated using the following command
448 dmalloc -p log-stats -p log-non-free -p log-bad-space -p log-elapsed-time \
449 -p check-fence -p check-heap -p check-lists -p check-blank \
450 -p check-funcs -p realloc-copy -p allow-free-null
452 Electric-fence support:
453 -----------------------
454 This enables compiling with Electric-fence support. Electric
455 fence is another very useful malloc debugging library which uses
456 your computer's virtual memory hardware to detect illegal memory
457 accesses. This support will make BusyBox be considerable larger
458 and run slower, so you should leave this option disabled unless
459 you are hunting a hard to find memory problem.
469 bool "Electric-fence"
474 bool "Enable obsolete features removed before SUSv3?"
477 This option will enable backwards compatibility with SuSv2,
478 specifically, old-style numeric options ('command -1 <file>')
479 will be supported in head, tail, and fold. (Note: should
484 menu 'Installation Options'
486 config INSTALL_NO_USR
487 bool "Don't use /usr"
490 Disable use of /usr. Don't activate this option if you don't know
491 that you really want this behaviour.
494 prompt "Applets links"
495 default INSTALL_APPLET_SYMLINKS
497 Choose how you install applets links.
499 config INSTALL_APPLET_SYMLINKS
502 Install applets as soft-links to the busybox binary. This needs some
503 free inodes on the filesystem, but might help with filesystem
504 generators that can't cope with hard-links.
506 config INSTALL_APPLET_HARDLINKS
509 Install applets as hard-links to the busybox binary. This might count
510 on a filesystem with few inodes.
512 config INSTALL_APPLET_SCRIPT_WRAPPERS
513 bool "as script wrappers"
515 Install applets as script wrappers that call the busybox binary.
517 config INSTALL_APPLET_DONT
519 depends on FEATURE_INSTALLER || FEATURE_SH_STANDALONE || FEATURE_PREFER_APPLETS
521 Do not install applet links. Useful when using the -install feature
522 or a standalone shell for rescue purposes.
527 prompt "/bin/sh applet link"
528 default INSTALL_SH_APPLET_SYMLINK
529 depends on INSTALL_APPLET_SCRIPT_WRAPPERS
531 Choose how you install /bin/sh applet link.
533 config INSTALL_SH_APPLET_SYMLINK
536 Install /bin/sh applet as soft-link to the busybox binary.
538 config INSTALL_SH_APPLET_HARDLINK
541 Install /bin/sh applet as hard-link to the busybox binary.
543 config INSTALL_SH_APPLET_SCRIPT_WRAPPER
544 bool "as script wrapper"
546 Install /bin/sh applet as script wrapper that call the busybox binary.
551 string "BusyBox installation prefix"
554 Define your directory to install BusyBox files/subdirs in.
558 source libbb/Config.in
564 source archival/Config.in
565 source coreutils/Config.in
566 source console-tools/Config.in
567 source debianutils/Config.in
568 source editors/Config.in
569 source findutils/Config.in
570 source init/Config.in
571 source loginutils/Config.in
572 source e2fsprogs/Config.in
573 source modutils/Config.in
574 source util-linux/Config.in
575 source miscutils/Config.in
576 source networking/Config.in
577 source procps/Config.in
578 source shell/Config.in
579 source sysklogd/Config.in
580 source runit/Config.in
581 source selinux/Config.in
582 source printutils/Config.in