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 prompt "Buffer allocation policy"
18 default CONFIG_FEATURE_BUFFERS_USE_MALLOC
20 There are 3 ways BusyBox can handle buffer allocations:
21 - Use malloc. This costs code size for the call to xmalloc.
22 - Put them on stack. For some very small machines with limited stack
23 space, this can be deadly. For most folks, this works just fine.
24 - Put them in BSS. This works beautifully for computers with a real
25 MMU (and OS support), but wastes runtime RAM for uCLinux. This
26 behavior was the only one available for BusyBox versions 0.48 and
29 config CONFIG_FEATURE_BUFFERS_USE_MALLOC
30 bool "Allocate with Malloc"
32 config CONFIG_FEATURE_BUFFERS_GO_ON_STACK
33 bool "Allocate on the Stack"
35 config CONFIG_FEATURE_BUFFERS_GO_IN_BSS
36 bool "Allocate in the .bss section"
40 config CONFIG_FEATURE_VERBOSE_USAGE
41 bool "Show verbose applet usage messages"
44 All BusyBox applets will show more verbose help messages when
45 busybox is invoked with --help. This will add a lot of text to the
46 busybox binary. In the default configuration, this will add about
47 13k, but it can add much more depending on your configuration.
49 config CONFIG_FEATURE_INSTALLER
50 bool "Support --install [-s] to install applet links at runtime"
53 Enable 'busybox --install [-s]' support. This will allow you to use
54 busybox at runtime to create hard links or symlinks for all the
55 applets that are compiled into busybox. This feature requires the
58 config CONFIG_LOCALE_SUPPORT
59 bool "Enable locale support (system needs locale for this to work)"
62 Enable this if your system has locale support and you would like
63 busybox to support locale settings.
65 config CONFIG_FEATURE_DEVFS
66 bool "Support for devfs"
69 Enable if you want BusyBox to work with devfs.
71 config CONFIG_FEATURE_DEVPTS
72 bool "Use the devpts filesystem for Unix98 PTYs"
73 default y if CONFIG_FEATURE_DEVFS
75 Enable if you want BusyBox to use Unix98 PTY support. If enabled,
76 busybox will use /dev/ptmx for the master side of the pseudoterminal
77 and /dev/pts/<number> for the slave side. Otherwise, BSD style
78 /dev/ttyp<number> will be used. To use this option, you should have
79 devpts or devfs mounted.
81 config CONFIG_FEATURE_CLEAN_UP
82 bool "Clean up all memory before exiting (usually not needed)"
85 As a size optimization, busybox normally exits without explicitly
86 freeing dynamically allocated memory or closing files. This saves
87 space since the OS will clean up for us, but it can confuse debuggers
88 like valgrind, which report tons of memory and resource leaks.
90 Don't enable this unless you have a really good reason to clean
93 config CONFIG_FEATURE_SUID
94 bool "Support for SUID/SGID handling"
97 Support SUID and SGID binaries.
99 config CONFIG_FEATURE_SUID_CONFIG
100 bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
101 default n if CONFIG_FEATURE_SUID
102 depends on CONFIG_FEATURE_SUID
104 Allow the SUID / SGID state of an applet to be determined runtime by
105 checking /etc/busybox.conf. The format of this file is as follows:
107 <applet> = [Ssx-][Ssx-][x-] (<username>|<uid>).(<groupname>|<gid>)
109 An example might help:
112 su = ssx root.0 # applet su can be run by anyone and runs with euid=0/egid=0
113 su = ssx # exactly the same
115 mount = sx- root.disk # applet mount can be run by root and members of group disk
116 # and runs with euid=0
118 cp = --- # disable applet cp for everyone
120 The file has to be owned by user root, group root and has to be
121 writeable only by root:
122 (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf)
123 The busybox executable has to be owned by user root, group
124 root and has to be setuid root for this to work:
125 (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox)
127 Robert 'sandman' Griebl has more information here:
128 <url: http://www.softforge.de/bb/suid.html >.
130 config CONFIG_FEATURE_SUID_CONFIG_QUIET
131 bool "Suppress warning message if /etc/busybox.conf is not readable"
133 depends on CONFIG_FEATURE_SUID_CONFIG
135 /etc/busybox.conf should be readable by the user needing the SUID, check
136 this option to avoid users to be notified about missing permissions.
138 config CONFIG_SELINUX
139 bool "Support NSA Security Enhanced Linux"
142 Enable support for SELinux in applets ls, ps, and id. Also provide
143 the option of compiling in SELinux applets.
145 If you do not have a complete SELinux userland installed, this stuff
146 will not compile. Go visit
147 http://www.nsa.gov/selinux/index.html
148 to download the necessary stuff to allow busybox to compile with
149 this option enabled. Specifially, libselinux 1.28 or better is
150 directly required by busybox. If the installation is located in a
151 non-standard directory, provide it by invoking make as follows:
152 CFLAGS=-I<libselinux-include-path> \
153 LDFLAGS=-L<libselinux-lib-path> \
156 Most people will leave this set to 'N'.
163 bool "Build BusyBox as a static binary (no shared libs)"
166 If you want to build a static BusyBox binary, which does not
167 use or require any shared libraries, then enable this option.
168 This can cause BusyBox to be considerably larger, so you should
169 leave this option false unless you have a good reason (i.e.
170 your target platform does not support shared libraries, or
171 you are building an initrd which doesn't need anything but
174 Most people will leave this set to 'N'.
176 # The busybox shared library feature is there so make standalone can produce
177 # smaller applets. Since make standalone isn't in yet, there's nothing using
178 # this yet, and so it's disabled.
179 config CONFIG_DISABLE_SHARED
183 config CONFIG_BUILD_LIBBUSYBOX
184 bool "Build shared libbusybox"
186 depends on CONFIG_DISABLE_SHARED
188 Build a shared library libbusybox.so which contains all
189 libraries used inside busybox.
191 config CONFIG_FEATURE_FULL_LIBBUSYBOX
192 bool "Feature-complete libbusybox"
193 default n if !CONFIG_FEATURE_SHARED_BUSYBOX
194 depends on CONFIG_BUILD_LIBBUSYBOX
196 Build a libbusybox with the complete feature-set, disregarding
197 the actually selected config.
199 Normally, libbusybox will only contain the features which are
200 used by busybox itself. If you plan to write a separate
201 standalone application which uses libbusybox say 'Y'.
203 Note: libbusybox is GPL, not LGPL, and exports no stable API that
204 might act as a copyright barrier. We can and will modify the
205 exported function set between releases (even minor version number
206 changes), and happily break out-of-tree features.
210 config CONFIG_FEATURE_SHARED_BUSYBOX
211 bool "Use shared libbusybox for busybox"
212 default y if CONFIG_BUILD_LIBBUSYBOX
213 depends on !CONFIG_STATIC && CONFIG_BUILD_LIBBUSYBOX
215 Use libbusybox.so also for busybox itself.
216 You need to have a working dynamic linker to use this variant.
219 bool "Build with Large File Support (for accessing files > 2 GB)"
221 select FDISK_SUPPORT_LARGE_DISKS
223 If you want to build BusyBox with large file support, then enable
224 this option. This will have no effect if your kernel or your C
225 library lacks large file support for large files. Some of the
226 programs that can benefit from large file support include dd, gzip,
227 cp, mount, tar, and many others. If you want to access files larger
228 than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'.
230 config USING_CROSS_COMPILER
231 bool "Do you want to build BusyBox with a Cross Compiler?"
234 Do you want to build BusyBox with a Cross Compiler? If so,
235 then enable this option. Otherwise leave it set to 'N'.
237 config CROSS_COMPILER_PREFIX
238 string "Cross Compiler prefix"
239 default "/usr/i386-linux-uclibc/bin/i386-uclibc-"
240 depends on USING_CROSS_COMPILER
242 If you want to build BusyBox with a cross compiler, then you
243 will need to set this to the cross-compiler prefix. For example,
244 if my cross-compiler is /usr/i386-linux-uclibc/bin/i386-uclibc-gcc
245 then I would enter '/usr/i386-linux-uclibc/bin/i386-uclibc-' here,
246 which will ensure the correct compiler is used.
248 config EXTRA_CFLAGS_OPTIONS
249 string "Any extra CFLAGS options for the compiler?"
252 Do you want to pass any extra CFLAGS options to the compiler as
253 you build BusyBox? If so, this is the option for you... For example,
254 if you want to add some simple compiler switches (like -march=i686),
255 or check for warnings using -Werror, just those options here.
257 config CONFIG_BUILD_AT_ONCE
258 bool "Compile all sources at once"
261 Normally each source-file is compiled with one invocation of
263 If you set this option, all sources are compiled at once.
264 This gives the compiler more opportunities to optimize which can
265 result in smaller and/or faster binaries.
267 Setting this option will consume alot of memory, e.g. if you
268 enable all applets with all features, gcc uses more than 300MB
269 RAM during compilation of busybox.
271 This option is most likely only beneficial for newer compilers
272 such as gcc-4.1 and above.
274 Say 'N' unless you know what you are doing.
278 menu 'Debugging Options'
281 bool "Build BusyBox with Debugging symbols"
284 Say Y here if you wish to compile BusyBox with debugging symbols.
285 This will allow you to use a debugger to examine BusyBox internals
286 while applets are running. This increases the size of the binary
287 considerably and should only be used when doing development.
288 If you are doing development and want to debug BusyBox, answer Y.
290 Most people should answer N.
293 prompt "Additional debugging library"
294 default CONFIG_NO_DEBUG_LIB
295 depends on CONFIG_DEBUG
297 Using an additional debugging library will make BusyBox become
298 considerable larger and will cause it to run more slowly. You
299 should always leave this option disabled for production use.
303 This enables compiling with dmalloc ( http://dmalloc.com/ )
304 which is an excellent public domain mem leak and malloc problem
305 detector. To enable dmalloc, before running busybox you will
306 want to properly set your environment, for example:
307 export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
308 The 'debug=' value is generated using the following command
309 dmalloc -p log-stats -p log-non-free -p log-bad-space -p log-elapsed-time \
310 -p check-fence -p check-heap -p check-lists -p check-blank \
311 -p check-funcs -p realloc-copy -p allow-free-null
313 Electric-fence support:
314 -----------------------
315 This enables compiling with Electric-fence support. Electric
316 fence is another very useful malloc debugging library which uses
317 your computer's virtual memory hardware to detect illegal memory
318 accesses. This support will make BusyBox be considerable larger
319 and run slower, so you should leave this option disabled unless
320 you are hunting a hard to find memory problem.
323 config CONFIG_NO_DEBUG_LIB
326 config CONFIG_DMALLOC
330 bool "Electric-fence"
334 config CONFIG_DEBUG_YANK_SUSv2
335 bool "Disable obsolete features removed before SUSv3?"
338 This option will disable backwards compatability with SuSv2,
339 specifically, old-style numeric options ('command -1 <file>')
340 will not be supported in head, tail, and fold. (Note: should
341 yank from renice too.)
345 menu 'Installation Options'
347 config CONFIG_INSTALL_NO_USR
348 bool "Don't use /usr"
351 Disable use of /usr. Don't activate this option if you don't know
352 that you really want this behaviour.
355 prompt "Applets links"
356 default CONFIG_INSTALL_APPLET_SYMLINKS
358 Choose how you install applets links.
360 config CONFIG_INSTALL_APPLET_SYMLINKS
363 Install applets as soft-links to the busybox binary. This needs some
364 free inodes on the filesystem, but might help with filesystem
365 generators that can't cope with hard-links.
367 config CONFIG_INSTALL_APPLET_HARDLINKS
370 Install applets as hard-links to the busybox binary. This might count
371 on a filesystem with few inodes.
373 config CONFIG_INSTALL_APPLET_DONT
375 prompt "not installed"
376 depends on CONFIG_FEATURE_INSTALLER || CONFIG_FEATURE_SH_STANDALONE_SHELL
378 Do not install applets links. Usefull when using the -install feature
379 or a standalone shell for rescue pruposes.
384 string "BusyBox installation prefix"
387 Define your directory to install BusyBox files/subdirs in.
391 source libbb/Config.in
397 source archival/Config.in
398 source coreutils/Config.in
399 source console-tools/Config.in
400 source debianutils/Config.in
401 source editors/Config.in
402 source findutils/Config.in
403 source init/Config.in
404 source loginutils/Config.in
405 source e2fsprogs/Config.in
406 source modutils/Config.in
407 source util-linux/Config.in
408 source miscutils/Config.in
409 source networking/Config.in
410 source procps/Config.in
411 source shell/Config.in
412 source sysklogd/Config.in