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 prompt "Buffer allocation policy"
34 default CONFIG_FEATURE_BUFFERS_USE_MALLOC
35 depends on CONFIG_NITPICK
37 There are 3 ways BusyBox can handle buffer allocations:
38 - Use malloc. This costs code size for the call to xmalloc.
39 - Put them on stack. For some very small machines with limited stack
40 space, this can be deadly. For most folks, this works just fine.
41 - Put them in BSS. This works beautifully for computers with a real
42 MMU (and OS support), but wastes runtime RAM for uCLinux. This
43 behavior was the only one available for BusyBox versions 0.48 and
46 config CONFIG_FEATURE_BUFFERS_USE_MALLOC
47 bool "Allocate with Malloc"
49 config CONFIG_FEATURE_BUFFERS_GO_ON_STACK
50 bool "Allocate on the Stack"
52 config CONFIG_FEATURE_BUFFERS_GO_IN_BSS
53 bool "Allocate in the .bss section"
57 config CONFIG_SHOW_USAGE
58 bool "Show terse applet usage messages"
61 All BusyBox applets will show help messages when invoked with
62 wrong arguments. You can turn off printing these terse usage
63 messages if you say no here.
64 This will save you up to 7k.
66 config CONFIG_FEATURE_VERBOSE_USAGE
67 bool "Show verbose applet usage messages"
69 select CONFIG_SHOW_USAGE
71 All BusyBox applets will show more verbose help messages when
72 busybox is invoked with --help. This will add a lot of text to the
73 busybox binary. In the default configuration, this will add about
74 13k, but it can add much more depending on your configuration.
76 config CONFIG_FEATURE_COMPRESS_USAGE
77 bool "Store applet usage messages in compressed form"
79 depends on CONFIG_SHOW_USAGE && CONFIG_NITPICK
81 Store usage messages in compressed form, uncompress them on-the-fly
82 when <applet> --help is called.
84 If you have a really tiny busybox with few applets enabled (and
85 bunzip2 isn't one of them), the overhead of the decompressor might
86 be noticeable. Also, if you run executables directly from ROM
87 and have very little memory, this might not be a win. Otherwise,
88 you probably want this.
90 config CONFIG_FEATURE_INSTALLER
91 bool "Support --install [-s] to install applet links at runtime"
94 Enable 'busybox --install [-s]' support. This will allow you to use
95 busybox at runtime to create hard links or symlinks for all the
96 applets that are compiled into busybox. This feature requires the
99 config CONFIG_LOCALE_SUPPORT
100 bool "Enable locale support (system needs locale for this to work)"
103 Enable this if your system has locale support and you would like
104 busybox to support locale settings.
106 config CONFIG_GETOPT_LONG
107 bool "Enable support for --long-options"
110 Enable this if you want busybox applets to use the gnu --long-option
111 style, in addition to single character -a -b -c style options.
113 config CONFIG_FEATURE_DEVPTS
114 bool "Use the devpts filesystem for Unix98 PTYs"
117 Enable if you want BusyBox to use Unix98 PTY support. If enabled,
118 busybox will use /dev/ptmx for the master side of the pseudoterminal
119 and /dev/pts/<number> for the slave side. Otherwise, BSD style
120 /dev/ttyp<number> will be used. To use this option, you should have
123 config CONFIG_FEATURE_CLEAN_UP
124 bool "Clean up all memory before exiting (usually not needed)"
126 depends on CONFIG_NITPICK
128 As a size optimization, busybox normally exits without explicitly
129 freeing dynamically allocated memory or closing files. This saves
130 space since the OS will clean up for us, but it can confuse debuggers
131 like valgrind, which report tons of memory and resource leaks.
133 Don't enable this unless you have a really good reason to clean
136 config CONFIG_FEATURE_SUID
137 bool "Support for SUID/SGID handling"
140 With this option you can install the busybox binary belonging
141 to root with the suid bit set, and it'll and it'll automatically drop
142 priviledges for applets that don't need root access.
144 If you're really paranoid and don't want to do this, build two
145 busybox binaries with different applets in them (and the appropriate
146 symlinks pointing to each binary), and only set the suid bit on the
147 one that needs it. The applets currently marked to need the suid bit
148 are login, passwd, su, ping, traceroute, crontab, dnsd, ipcrm, ipcs,
151 config CONFIG_FEATURE_SUID_CONFIG
152 bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
153 default n if CONFIG_FEATURE_SUID
154 depends on CONFIG_FEATURE_SUID
156 Allow the SUID / SGID state of an applet to be determined at runtime
157 by checking /etc/busybox.conf. (This is sort of a poor man's sudo.)
158 The format of this file is as follows:
160 <applet> = [Ssx-][Ssx-][x-] (<username>|<uid>).(<groupname>|<gid>)
162 An example might help:
165 su = ssx root.0 # applet su can be run by anyone and runs with euid=0/egid=0
166 su = ssx # exactly the same
168 mount = sx- root.disk # applet mount can be run by root and members of group disk
169 # and runs with euid=0
171 cp = --- # disable applet cp for everyone
173 The file has to be owned by user root, group root and has to be
174 writeable only by root:
175 (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf)
176 The busybox executable has to be owned by user root, group
177 root and has to be setuid root for this to work:
178 (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox)
180 Robert 'sandman' Griebl has more information here:
181 <url: http://www.softforge.de/bb/suid.html >.
183 config CONFIG_FEATURE_SUID_CONFIG_QUIET
184 bool "Suppress warning message if /etc/busybox.conf is not readable"
186 depends on CONFIG_FEATURE_SUID_CONFIG
188 /etc/busybox.conf should be readable by the user needing the SUID, check
189 this option to avoid users to be notified about missing permissions.
191 config CONFIG_SELINUX
192 bool "Support NSA Security Enhanced Linux"
195 Enable support for SELinux in applets ls, ps, and id. Also provide
196 the option of compiling in SELinux applets.
198 If you do not have a complete SELinux userland installed, this stuff
199 will not compile. Go visit
200 http://www.nsa.gov/selinux/index.html
201 to download the necessary stuff to allow busybox to compile with
202 this option enabled. Specifially, libselinux 1.28 or better is
203 directly required by busybox. If the installation is located in a
204 non-standard directory, provide it by invoking make as follows:
205 CFLAGS=-I<libselinux-include-path> \
206 LDFLAGS=-L<libselinux-lib-path> \
209 Most people will leave this set to 'N'.
211 config CONFIG_BUSYBOX_EXEC_PATH
212 string "Path to BusyBox executable"
213 default "/proc/self/exe"
215 When Busybox applets need to run other busybox applets, BusyBox
216 sometimes needs to exec() itself. When the /proc filesystem is
217 mounted, /proc/self/exe always points to the currently running
218 executable. If you haven't got /proc, set this to wherever you
219 want to run BusyBox from.
226 bool "Build BusyBox as a static binary (no shared libs)"
229 If you want to build a static BusyBox binary, which does not
230 use or require any shared libraries, then enable this option.
231 This can cause BusyBox to be considerably larger, so you should
232 leave this option false unless you have a good reason (i.e.
233 your target platform does not support shared libraries, or
234 you are building an initrd which doesn't need anything but
237 Most people will leave this set to 'N'.
239 config CONFIG_BUILD_LIBBUSYBOX
240 bool "Build shared libbusybox"
241 depends on CONFIG_STANDALONE
244 Build a shared library libbusybox.so which contains all
245 libraries used inside busybox.
247 config CONFIG_FEATURE_FULL_LIBBUSYBOX
248 bool "Feature-complete libbusybox"
249 default n if !CONFIG_FEATURE_SHARED_BUSYBOX
250 depends on CONFIG_BUILD_LIBBUSYBOX
252 Build a libbusybox with the complete feature-set, disregarding
253 the actually selected config.
255 Normally, libbusybox will only contain the features which are
256 used by busybox itself. If you plan to write a separate
257 standalone application which uses libbusybox say 'Y'.
259 Note: libbusybox is GPL, not LGPL, and exports no stable API that
260 might act as a copyright barrier. We can and will modify the
261 exported function set between releases (even minor version number
262 changes), and happily break out-of-tree features.
266 config CONFIG_FEATURE_SHARED_BUSYBOX
267 bool "Use shared libbusybox for busybox"
268 default y if CONFIG_BUILD_LIBBUSYBOX
269 depends on !CONFIG_STATIC && CONFIG_BUILD_LIBBUSYBOX
271 Use libbusybox.so also for busybox itself.
272 You need to have a working dynamic linker to use this variant.
275 bool "Build with Large File Support (for accessing files > 2 GB)"
277 select FDISK_SUPPORT_LARGE_DISKS
279 If you want to build BusyBox with large file support, then enable
280 this option. This will have no effect if your kernel or your C
281 library lacks large file support for large files. Some of the
282 programs that can benefit from large file support include dd, gzip,
283 cp, mount, tar, and many others. If you want to access files larger
284 than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'.
286 config USING_CROSS_COMPILER
287 bool "Do you want to build BusyBox with a Cross Compiler?"
290 Do you want to build BusyBox with a Cross Compiler? If so,
291 then enable this option. Otherwise leave it set to 'N'.
293 config CROSS_COMPILER_PREFIX
294 string "Cross Compiler prefix"
295 default "/usr/i386-linux-uclibc/bin/i386-uclibc-"
296 depends on USING_CROSS_COMPILER
298 If you want to build BusyBox with a cross compiler, then you
299 will need to set this to the cross-compiler prefix. For example,
300 if my cross-compiler is /usr/i386-linux-uclibc/bin/i386-uclibc-gcc
301 then I would enter '/usr/i386-linux-uclibc/bin/i386-uclibc-' here,
302 which will ensure the correct compiler is used.
304 config EXTRA_CFLAGS_OPTIONS
305 string "Any extra CFLAGS options for the compiler?"
308 Do you want to pass any extra CFLAGS options to the compiler as
309 you build BusyBox? If so, this is the option for you... For example,
310 if you want to add some simple compiler switches (like -march=i686),
311 or check for warnings using -Werror, just those options here.
313 config CONFIG_BUILD_AT_ONCE
314 bool "Compile all sources at once"
317 Normally each source-file is compiled with one invocation of
319 If you set this option, all sources are compiled at once.
320 This gives the compiler more opportunities to optimize which can
321 result in smaller and/or faster binaries.
323 Setting this option will consume alot of memory, e.g. if you
324 enable all applets with all features, gcc uses more than 300MB
325 RAM during compilation of busybox.
327 This option is most likely only beneficial for newer compilers
328 such as gcc-4.1 and above.
330 Say 'N' unless you know what you are doing.
334 menu 'Debugging Options'
337 bool "Build BusyBox with extra Debugging symbols"
340 Say Y here if you wish to examine BusyBox internals while applets are
341 running. This increases the size of the binary considerably, and
342 should only be used when doing development. If you are doing
343 development and want to debug BusyBox, answer Y.
345 Most people should answer N.
347 config CONFIG_DEBUG_PESSIMIZE
348 bool "Disable compiler optimizations."
350 depends on CONFIG_DEBUG
352 The compiler's optimization of source code can eliminate and reorder
353 code, resulting in an executable that's hard to understand when
354 stepping through it with a debugger. This switches it off, resulting
355 in a much bigger executable that more closely matches the source
359 prompt "Additional debugging library"
360 default CONFIG_NO_DEBUG_LIB
361 depends on CONFIG_DEBUG
363 Using an additional debugging library will make BusyBox become
364 considerable larger and will cause it to run more slowly. You
365 should always leave this option disabled for production use.
369 This enables compiling with dmalloc ( http://dmalloc.com/ )
370 which is an excellent public domain mem leak and malloc problem
371 detector. To enable dmalloc, before running busybox you will
372 want to properly set your environment, for example:
373 export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
374 The 'debug=' value is generated using the following command
375 dmalloc -p log-stats -p log-non-free -p log-bad-space -p log-elapsed-time \
376 -p check-fence -p check-heap -p check-lists -p check-blank \
377 -p check-funcs -p realloc-copy -p allow-free-null
379 Electric-fence support:
380 -----------------------
381 This enables compiling with Electric-fence support. Electric
382 fence is another very useful malloc debugging library which uses
383 your computer's virtual memory hardware to detect illegal memory
384 accesses. This support will make BusyBox be considerable larger
385 and run slower, so you should leave this option disabled unless
386 you are hunting a hard to find memory problem.
389 config CONFIG_NO_DEBUG_LIB
392 config CONFIG_DMALLOC
396 bool "Electric-fence"
400 config CONFIG_DEBUG_YANK_SUSv2
401 bool "Disable obsolete features removed before SUSv3?"
404 This option will disable backwards compatibility with SuSv2,
405 specifically, old-style numeric options ('command -1 <file>')
406 will not be supported in head, tail, and fold. (Note: should
407 yank from renice too.)
411 menu 'Installation Options'
413 config CONFIG_INSTALL_NO_USR
414 bool "Don't use /usr"
417 Disable use of /usr. Don't activate this option if you don't know
418 that you really want this behaviour.
421 prompt "Applets links"
422 default CONFIG_INSTALL_APPLET_SYMLINKS
424 Choose how you install applets links.
426 config CONFIG_INSTALL_APPLET_SYMLINKS
429 Install applets as soft-links to the busybox binary. This needs some
430 free inodes on the filesystem, but might help with filesystem
431 generators that can't cope with hard-links.
433 config CONFIG_INSTALL_APPLET_HARDLINKS
436 Install applets as hard-links to the busybox binary. This might count
437 on a filesystem with few inodes.
439 config CONFIG_INSTALL_APPLET_DONT
441 prompt "not installed"
442 depends on CONFIG_FEATURE_INSTALLER || CONFIG_FEATURE_SH_STANDALONE_SHELL
444 Do not install applets links. Usefull when using the -install feature
445 or a standalone shell for rescue pruposes.
450 string "BusyBox installation prefix"
453 Define your directory to install BusyBox files/subdirs in.
457 source libbb/Config.in
463 source archival/Config.in
464 source coreutils/Config.in
465 source console-tools/Config.in
466 source debianutils/Config.in
467 source editors/Config.in
468 source findutils/Config.in
469 source init/Config.in
470 source loginutils/Config.in
471 source e2fsprogs/Config.in
472 source modutils/Config.in
473 source util-linux/Config.in
474 source miscutils/Config.in
475 source networking/Config.in
476 source procps/Config.in
477 source shell/Config.in
478 source sysklogd/Config.in