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. This feature requires the
107 config LOCALE_SUPPORT
108 bool "Enable locale support (system needs locale for this to work)"
111 Enable this if your system has locale support and you would like
112 busybox to support locale settings.
117 # bool "Enable support for --long-options"
120 # Enable this if you want busybox applets to use the gnu --long-option
121 # style, in addition to single character -a -b -c style options.
123 config FEATURE_DEVPTS
124 bool "Use the devpts filesystem for Unix98 PTYs"
127 Enable if you want BusyBox to use Unix98 PTY support. If enabled,
128 busybox will use /dev/ptmx for the master side of the pseudoterminal
129 and /dev/pts/<number> for the slave side. Otherwise, BSD style
130 /dev/ttyp<number> will be used. To use this option, you should have
133 config FEATURE_CLEAN_UP
134 bool "Clean up all memory before exiting (usually not needed)"
138 As a size optimization, busybox normally exits without explicitly
139 freeing dynamically allocated memory or closing files. This saves
140 space since the OS will clean up for us, but it can confuse debuggers
141 like valgrind, which report tons of memory and resource leaks.
143 Don't enable this unless you have a really good reason to clean
147 bool "Support for SUID/SGID handling"
150 With this option you can install the busybox binary belonging
151 to root with the suid bit set, and it'll and it'll automatically drop
152 priviledges for applets that don't need root access.
154 If you're really paranoid and don't want to do this, build two
155 busybox binaries with different applets in them (and the appropriate
156 symlinks pointing to each binary), and only set the suid bit on the
157 one that needs it. The applets currently marked to need the suid bit
158 are login, passwd, su, ping, traceroute, crontab, dnsd, ipcrm, ipcs,
161 config FEATURE_SYSLOG
162 bool "Support for syslog"
165 This option is auto-selected when you select any applet which may
166 send its output to syslog. You do not need to select it manually.
168 config FEATURE_SUID_CONFIG
169 bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
170 default n if FEATURE_SUID
171 depends on FEATURE_SUID
173 Allow the SUID / SGID state of an applet to be determined at runtime
174 by checking /etc/busybox.conf. (This is sort of a poor man's sudo.)
175 The format of this file is as follows:
177 <applet> = [Ssx-][Ssx-][x-] (<username>|<uid>).(<groupname>|<gid>)
179 An example might help:
182 su = ssx root.0 # applet su can be run by anyone and runs with euid=0/egid=0
183 su = ssx # exactly the same
185 mount = sx- root.disk # applet mount can be run by root and members of group disk
186 # and runs with euid=0
188 cp = --- # disable applet cp for everyone
190 The file has to be owned by user root, group root and has to be
191 writeable only by root:
192 (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf)
193 The busybox executable has to be owned by user root, group
194 root and has to be setuid root for this to work:
195 (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox)
197 Robert 'sandman' Griebl has more information here:
198 <url: http://www.softforge.de/bb/suid.html >.
200 config FEATURE_SUID_CONFIG_QUIET
201 bool "Suppress warning message if /etc/busybox.conf is not readable"
203 depends on FEATURE_SUID_CONFIG
205 /etc/busybox.conf should be readable by the user needing the SUID, check
206 this option to avoid users to be notified about missing permissions.
209 bool "Support NSA Security Enhanced Linux"
212 Enable support for SELinux in applets ls, ps, and id. Also provide
213 the option of compiling in SELinux applets.
215 If you do not have a complete SELinux userland installed, this stuff
216 will not compile. Go visit
217 http://www.nsa.gov/selinux/index.html
218 to download the necessary stuff to allow busybox to compile with
219 this option enabled. Specifially, libselinux 1.28 or better is
220 directly required by busybox. If the installation is located in a
221 non-standard directory, provide it by invoking make as follows:
222 CFLAGS=-I<libselinux-include-path> \
223 LDFLAGS=-L<libselinux-lib-path> \
226 Most people will leave this set to 'N'.
228 config BUSYBOX_EXEC_PATH
229 string "Path to BusyBox executable"
230 default "/proc/self/exe"
232 When Busybox applets need to run other busybox applets, BusyBox
233 sometimes needs to exec() itself. When the /proc filesystem is
234 mounted, /proc/self/exe always points to the currently running
235 executable. If you haven't got /proc, set this to wherever you
236 want to run BusyBox from.
243 bool "Build BusyBox as a static binary (no shared libs)"
246 If you want to build a static BusyBox binary, which does not
247 use or require any shared libraries, then enable this option.
248 This can cause BusyBox to be considerably larger, so you should
249 leave this option false unless you have a good reason (i.e.
250 your target platform does not support shared libraries, or
251 you are building an initrd which doesn't need anything but
254 Most people will leave this set to 'N'.
256 config BUILD_LIBBUSYBOX
257 bool "Build shared libbusybox"
260 Build a shared library libbusybox.so which contains all
261 libraries used inside busybox.
263 This is an experimental feature intended to support the upcoming
264 "make standalone" mode. Enabling it against the one big busybox
265 binary serves no purpose (and increases the size). You should
266 almost certainly say "no" to this right now.
268 config FEATURE_FULL_LIBBUSYBOX
269 bool "Feature-complete libbusybox"
270 default n if !FEATURE_SHARED_BUSYBOX
271 depends on BUILD_LIBBUSYBOX
273 Build a libbusybox with the complete feature-set, disregarding
274 the actually selected config.
276 Normally, libbusybox will only contain the features which are
277 used by busybox itself. If you plan to write a separate
278 standalone application which uses libbusybox say 'Y'.
280 Note: libbusybox is GPL, not LGPL, and exports no stable API that
281 might act as a copyright barrier. We can and will modify the
282 exported function set between releases (even minor version number
283 changes), and happily break out-of-tree features.
287 config FEATURE_SHARED_BUSYBOX
288 bool "Use shared libbusybox for busybox"
289 default y if BUILD_LIBBUSYBOX
290 depends on !STATIC && BUILD_LIBBUSYBOX
292 Use libbusybox.so also for busybox itself.
293 You need to have a working dynamic linker to use this variant.
296 bool "Build with Large File Support (for accessing files > 2 GB)"
298 select FDISK_SUPPORT_LARGE_DISKS
300 If you want to build BusyBox with large file support, then enable
301 this option. This will have no effect if your kernel or your C
302 library lacks large file support for large files. Some of the
303 programs that can benefit from large file support include dd, gzip,
304 cp, mount, tar, and many others. If you want to access files larger
305 than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'.
308 bool "Compile all sources at once"
311 Normally each source-file is compiled with one invocation of
313 If you set this option, all sources are compiled at once.
314 This gives the compiler more opportunities to optimize which can
315 result in smaller and/or faster binaries.
317 Setting this option will consume alot of memory, e.g. if you
318 enable all applets with all features, gcc uses more than 300MB
319 RAM during compilation of busybox.
321 This option is most likely only beneficial for newer compilers
322 such as gcc-4.1 and above.
324 Say 'N' unless you know what you are doing.
328 menu 'Debugging Options'
331 bool "Build BusyBox with extra Debugging symbols"
334 Say Y here if you wish to examine BusyBox internals while applets are
335 running. This increases the size of the binary considerably, and
336 should only be used when doing development. If you are doing
337 development and want to debug BusyBox, answer Y.
339 Most people should answer N.
341 config DEBUG_PESSIMIZE
342 bool "Disable compiler optimizations."
346 The compiler's optimization of source code can eliminate and reorder
347 code, resulting in an executable that's hard to understand when
348 stepping through it with a debugger. This switches it off, resulting
349 in a much bigger executable that more closely matches the source
353 prompt "Additional debugging library"
357 Using an additional debugging library will make BusyBox become
358 considerable larger and will cause it to run more slowly. You
359 should always leave this option disabled for production use.
363 This enables compiling with dmalloc ( http://dmalloc.com/ )
364 which is an excellent public domain mem leak and malloc problem
365 detector. To enable dmalloc, before running busybox you will
366 want to properly set your environment, for example:
367 export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
368 The 'debug=' value is generated using the following command
369 dmalloc -p log-stats -p log-non-free -p log-bad-space -p log-elapsed-time \
370 -p check-fence -p check-heap -p check-lists -p check-blank \
371 -p check-funcs -p realloc-copy -p allow-free-null
373 Electric-fence support:
374 -----------------------
375 This enables compiling with Electric-fence support. Electric
376 fence is another very useful malloc debugging library which uses
377 your computer's virtual memory hardware to detect illegal memory
378 accesses. This support will make BusyBox be considerable larger
379 and run slower, so you should leave this option disabled unless
380 you are hunting a hard to find memory problem.
390 bool "Electric-fence"
394 config DEBUG_YANK_SUSv2
395 bool "Disable obsolete features removed before SUSv3?"
398 This option will disable backwards compatibility with SuSv2,
399 specifically, old-style numeric options ('command -1 <file>')
400 will not be supported in head, tail, and fold. (Note: should
401 yank from renice too.)
405 menu 'Installation Options'
407 config INSTALL_NO_USR
408 bool "Don't use /usr"
411 Disable use of /usr. Don't activate this option if you don't know
412 that you really want this behaviour.
415 prompt "Applets links"
416 default INSTALL_APPLET_SYMLINKS
418 Choose how you install applets links.
420 config INSTALL_APPLET_SYMLINKS
423 Install applets as soft-links to the busybox binary. This needs some
424 free inodes on the filesystem, but might help with filesystem
425 generators that can't cope with hard-links.
427 config INSTALL_APPLET_HARDLINKS
430 Install applets as hard-links to the busybox binary. This might count
431 on a filesystem with few inodes.
433 config INSTALL_APPLET_DONT
435 prompt "not installed"
436 depends on FEATURE_INSTALLER || FEATURE_SH_STANDALONE_SHELL
438 Do not install applets links. Usefull when using the -install feature
439 or a standalone shell for rescue pruposes.
444 string "BusyBox installation prefix"
447 Define your directory to install BusyBox files/subdirs in.
451 source libbb/Config.in
457 source archival/Config.in
458 source coreutils/Config.in
459 source console-tools/Config.in
460 source debianutils/Config.in
461 source editors/Config.in
462 source findutils/Config.in
463 source init/Config.in
464 source loginutils/Config.in
465 source e2fsprogs/Config.in
466 source modutils/Config.in
467 source util-linux/Config.in
468 source miscutils/Config.in
469 source networking/Config.in
470 source procps/Config.in
471 source shell/Config.in
472 source sysklogd/Config.in
473 source runit/Config.in