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 "See lots more (probably unnecessary) configuration options."
20 Some BusyBox applets have more configuration options than anyone
21 will ever care about. To avoid drowining people in complexity, most
22 of the applet features that can be set to a sane default value are
23 hidden, unless you hit the above switch.
25 This is better than to telling people to edit the busybox source
26 code, but not by much.
28 See http://en.wikipedia.org/wiki/Fibber_McGee_and_Molly#The_Closet
33 bool "Enable options for full-blown desktop systems"
36 Enable options and features which are not essential.
37 Select this only if you plan to use busybox on full-blown
38 desktop machine with common Linux distro, not on an embedded box.
41 prompt "Buffer allocation policy"
42 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.
114 bool "Enable support for --long-options"
117 Enable this if you want busybox applets to use the gnu --long-option
118 style, in addition to single character -a -b -c style options.
120 config FEATURE_DEVPTS
121 bool "Use the devpts filesystem for Unix98 PTYs"
124 Enable if you want BusyBox to use Unix98 PTY support. If enabled,
125 busybox will use /dev/ptmx for the master side of the pseudoterminal
126 and /dev/pts/<number> for the slave side. Otherwise, BSD style
127 /dev/ttyp<number> will be used. To use this option, you should have
130 config FEATURE_CLEAN_UP
131 bool "Clean up all memory before exiting (usually not needed)"
135 As a size optimization, busybox normally exits without explicitly
136 freeing dynamically allocated memory or closing files. This saves
137 space since the OS will clean up for us, but it can confuse debuggers
138 like valgrind, which report tons of memory and resource leaks.
140 Don't enable this unless you have a really good reason to clean
143 config FEATURE_PIDFILE
144 bool "Support writing pidfiles"
147 This option makes some applets (e.g. crond, syslogd, inetd) write
148 a pidfile in /var/run. Some applications rely on them.
151 bool "Support for SUID/SGID handling"
154 With this option you can install the busybox binary belonging
155 to root with the suid bit set, and it'll and it'll automatically drop
156 priviledges for applets that don't need root access.
158 If you're really paranoid and don't want to do this, build two
159 busybox binaries with different applets in them (and the appropriate
160 symlinks pointing to each binary), and only set the suid bit on the
161 one that needs it. The applets currently marked to need the suid bit
162 are login, passwd, su, ping, traceroute, crontab, dnsd, ipcrm, ipcs,
165 config FEATURE_SUID_CONFIG
166 bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
167 default n if FEATURE_SUID
168 depends on FEATURE_SUID
170 Allow the SUID / SGID state of an applet to be determined at runtime
171 by checking /etc/busybox.conf. (This is sort of a poor man's sudo.)
172 The format of this file is as follows:
174 <applet> = [Ssx-][Ssx-][x-] (<username>|<uid>).(<groupname>|<gid>)
176 An example might help:
179 su = ssx root.0 # applet su can be run by anyone and runs with euid=0/egid=0
180 su = ssx # exactly the same
182 mount = sx- root.disk # applet mount can be run by root and members of group disk
183 # and runs with euid=0
185 cp = --- # disable applet cp for everyone
187 The file has to be owned by user root, group root and has to be
188 writeable only by root:
189 (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf)
190 The busybox executable has to be owned by user root, group
191 root and has to be setuid root for this to work:
192 (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox)
194 Robert 'sandman' Griebl has more information here:
195 <url: http://www.softforge.de/bb/suid.html >.
197 config FEATURE_SUID_CONFIG_QUIET
198 bool "Suppress warning message if /etc/busybox.conf is not readable"
200 depends on FEATURE_SUID_CONFIG
202 /etc/busybox.conf should be readable by the user needing the SUID, check
203 this option to avoid users to be notified about missing permissions.
206 bool "Support NSA Security Enhanced Linux"
209 Enable support for SELinux in applets ls, ps, and id. Also provide
210 the option of compiling in SELinux applets.
212 If you do not have a complete SELinux userland installed, this stuff
213 will not compile. Go visit
214 http://www.nsa.gov/selinux/index.html
215 to download the necessary stuff to allow busybox to compile with
216 this option enabled. Specifially, libselinux 1.28 or better is
217 directly required by busybox. If the installation is located in a
218 non-standard directory, provide it by invoking make as follows:
219 CFLAGS=-I<libselinux-include-path> \
220 LDFLAGS=-L<libselinux-lib-path> \
223 Most people will leave this set to 'N'.
225 config FEATURE_PREFER_APPLETS
226 bool "exec prefers applets"
229 This is an experimental option which directs applets about to
230 call 'exec' to try and find an applicable busybox applet before
231 searching the PATH. This is typically done by exec'ing
233 This may affect shell, find -exec, xargs and similar applets.
234 They will use applets even if /bin/<applet> -> busybox link
235 is missing (or is not a link to busybox). However, this causes
236 problems in chroot jails without mounted /proc and with ps/top
237 (command name can be shown as 'exe' for applets started this way).
239 config BUSYBOX_EXEC_PATH
240 string "Path to BusyBox executable"
241 default "/proc/self/exe"
243 When Busybox applets need to run other busybox applets, BusyBox
244 sometimes needs to exec() itself. When the /proc filesystem is
245 mounted, /proc/self/exe always points to the currently running
246 executable. If you haven't got /proc, set this to wherever you
247 want to run BusyBox from.
249 # These are auto-selected by other options
251 config FEATURE_SYSLOG
252 bool "Support for logging to syslog"
255 This option is auto-selected when you select any applet which may
256 send its output to syslog. You do not need to select it manually.
258 config FEATURE_HAVE_RPC
262 This is automatically selected if any of enabled applets need it.
263 You do not need to select it manually.
270 bool "Build BusyBox as a static binary (no shared libs)"
273 If you want to build a static BusyBox binary, which does not
274 use or require any shared libraries, then enable this option.
275 This can cause BusyBox to be considerably larger, so you should
276 leave this option false unless you have a good reason (i.e.
277 your target platform does not support shared libraries, or
278 you are building an initrd which doesn't need anything but
281 Most people will leave this set to 'N'.
283 config BUILD_LIBBUSYBOX
284 bool "Build shared libbusybox"
287 Build a shared library libbusybox.so which contains all
288 libraries used inside busybox.
290 This is an experimental feature intended to support the upcoming
291 "make standalone" mode. Enabling it against the one big busybox
292 binary serves no purpose (and increases the size). You should
293 almost certainly say "no" to this right now.
295 config FEATURE_FULL_LIBBUSYBOX
296 bool "Feature-complete libbusybox"
297 default n if !FEATURE_SHARED_BUSYBOX
298 depends on BUILD_LIBBUSYBOX
300 Build a libbusybox with the complete feature-set, disregarding
301 the actually selected config.
303 Normally, libbusybox will only contain the features which are
304 used by busybox itself. If you plan to write a separate
305 standalone application which uses libbusybox say 'Y'.
307 Note: libbusybox is GPL, not LGPL, and exports no stable API that
308 might act as a copyright barrier. We can and will modify the
309 exported function set between releases (even minor version number
310 changes), and happily break out-of-tree features.
314 config FEATURE_SHARED_BUSYBOX
315 bool "Use shared libbusybox for busybox"
316 default y if BUILD_LIBBUSYBOX
317 depends on !STATIC && BUILD_LIBBUSYBOX
319 Use libbusybox.so also for busybox itself.
320 You need to have a working dynamic linker to use this variant.
323 bool "Build with Large File Support (for accessing files > 2 GB)"
325 select FDISK_SUPPORT_LARGE_DISKS
327 If you want to build BusyBox with large file support, then enable
328 this option. This will have no effect if your kernel or your C
329 library lacks large file support for large files. Some of the
330 programs that can benefit from large file support include dd, gzip,
331 cp, mount, tar, and many others. If you want to access files larger
332 than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'.
335 bool "Compile all sources at once"
338 Normally each source-file is compiled with one invocation of
340 If you set this option, all sources are compiled at once.
341 This gives the compiler more opportunities to optimize which can
342 result in smaller and/or faster binaries.
344 Setting this option will consume alot of memory, e.g. if you
345 enable all applets with all features, gcc uses more than 300MB
346 RAM during compilation of busybox.
348 This option is most likely only beneficial for newer compilers
349 such as gcc-4.1 and above.
351 Say 'N' unless you know what you are doing.
355 menu 'Debugging Options'
358 bool "Build BusyBox with extra Debugging symbols"
361 Say Y here if you wish to examine BusyBox internals while applets are
362 running. This increases the size of the binary considerably, and
363 should only be used when doing development. If you are doing
364 development and want to debug BusyBox, answer Y.
366 Most people should answer N.
369 bool "Abort compilation on any warning"
372 Selecting this will add -Werror to gcc command line.
374 Most people should answer N.
377 #config DEBUG_PESSIMIZE
378 # bool "Disable compiler optimizations."
382 # The compiler's optimization of source code can eliminate and reorder
383 # code, resulting in an executable that's hard to understand when
384 # stepping through it with a debugger. This switches it off, resulting
385 # in a much bigger executable that more closely matches the source
389 prompt "Additional debugging library"
392 Using an additional debugging library will make BusyBox become
393 considerable larger and will cause it to run more slowly. You
394 should always leave this option disabled for production use.
398 This enables compiling with dmalloc ( http://dmalloc.com/ )
399 which is an excellent public domain mem leak and malloc problem
400 detector. To enable dmalloc, before running busybox you will
401 want to properly set your environment, for example:
402 export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
403 The 'debug=' value is generated using the following command
404 dmalloc -p log-stats -p log-non-free -p log-bad-space -p log-elapsed-time \
405 -p check-fence -p check-heap -p check-lists -p check-blank \
406 -p check-funcs -p realloc-copy -p allow-free-null
408 Electric-fence support:
409 -----------------------
410 This enables compiling with Electric-fence support. Electric
411 fence is another very useful malloc debugging library which uses
412 your computer's virtual memory hardware to detect illegal memory
413 accesses. This support will make BusyBox be considerable larger
414 and run slower, so you should leave this option disabled unless
415 you are hunting a hard to find memory problem.
425 bool "Electric-fence"
430 bool "Enable obsolete features removed before SUSv3?"
433 This option will enable backwards compatibility with SuSv2,
434 specifically, old-style numeric options ('command -1 <file>')
435 will be supported in head, tail, and fold. (Note: should
440 menu 'Installation Options'
442 config INSTALL_NO_USR
443 bool "Don't use /usr"
446 Disable use of /usr. Don't activate this option if you don't know
447 that you really want this behaviour.
450 prompt "Applets links"
451 default INSTALL_APPLET_SYMLINKS
453 Choose how you install applets links.
455 config INSTALL_APPLET_SYMLINKS
458 Install applets as soft-links to the busybox binary. This needs some
459 free inodes on the filesystem, but might help with filesystem
460 generators that can't cope with hard-links.
462 config INSTALL_APPLET_HARDLINKS
465 Install applets as hard-links to the busybox binary. This might count
466 on a filesystem with few inodes.
468 config INSTALL_APPLET_SCRIPT_WRAPPERS
469 bool "as script wrappers"
471 Install applets as script wrappers that call the busybox binary.
473 config INSTALL_APPLET_DONT
475 depends on FEATURE_INSTALLER || FEATURE_SH_STANDALONE || FEATURE_PREFER_APPLETS
477 Do not install applet links. Useful when using the -install feature
478 or a standalone shell for rescue purposes.
483 prompt "/bin/sh applet link"
484 default INSTALL_SH_APPLET_SYMLINK
485 depends on INSTALL_APPLET_SCRIPT_WRAPPERS
487 Choose how you install /bin/sh applet link.
489 config INSTALL_SH_APPLET_SYMLINK
492 Install /bin/sh applet as soft-link to the busybox binary.
494 config INSTALL_SH_APPLET_HARDLINK
497 Install /bin/sh applet as hard-link to the busybox binary.
499 config INSTALL_SH_APPLET_SCRIPT_WRAPPER
500 bool "as script wrapper"
502 Install /bin/sh applet as script wrapper that call the busybox binary.
507 string "BusyBox installation prefix"
510 Define your directory to install BusyBox files/subdirs in.
514 source libbb/Config.in
520 source archival/Config.in
521 source coreutils/Config.in
522 source console-tools/Config.in
523 source debianutils/Config.in
524 source editors/Config.in
525 source findutils/Config.in
526 source init/Config.in
527 source loginutils/Config.in
528 source e2fsprogs/Config.in
529 source modutils/Config.in
530 source util-linux/Config.in
531 source miscutils/Config.in
532 source networking/Config.in
533 source procps/Config.in
534 source shell/Config.in
535 source sysklogd/Config.in
536 source runit/Config.in
537 source selinux/Config.in
538 source ipsvd/Config.in