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 SE Linux in applets ls, ps, and id. Also provide
143 the option of compiling in SE Linux applets.
145 If you do not have a complete SE Linux Full Userland installed, this
146 stuff 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 this
151 Most people will leave this set to 'N'.
158 bool "Build BusyBox as a static binary (no shared libs)"
161 If you want to build a static BusyBox binary, which does not
162 use or require any shared libraries, then enable this option.
163 This can cause BusyBox to be considerably larger, so you should
164 leave this option false unless you have a good reason (i.e.
165 your target platform does not support shared libraries, or
166 you are building an initrd which doesn't need anything but
169 Most people will leave this set to 'N'.
171 config CONFIG_BUILD_LIBBUSYBOX
172 bool "Build shared libbusybox"
175 Build a shared library libbusybox.so which contains all
176 libraries used inside busybox.
178 config CONFIG_FEATURE_FULL_LIBBUSYBOX
179 bool "Feature-complete libbusybox"
180 default n if !CONFIG_FEATURE_SHARED_BUSYBOX
181 depends on CONFIG_BUILD_LIBBUSYBOX
183 Build a libbusybox with the complete feature-set, disregarding
184 the actually selected config.
186 Normally, libbusybox will only contain the features which are
187 used by busybox itself. If you plan to write a separate
188 standalone application which uses libbusybox say 'Y'.
190 Note: libbusybox is GPL, not LGPL, and exports no stable API that
191 might act as a copyright barrier. We can and will modify the
192 exported function set between releases (even minor version number
193 changes), and happily break out-of-tree features.
197 config CONFIG_FEATURE_SHARED_BUSYBOX
198 bool "Use shared libbusybox for busybox"
199 default y if CONFIG_BUILD_LIBBUSYBOX
200 depends on !CONFIG_STATIC && CONFIG_BUILD_LIBBUSYBOX
202 Use libbusybox.so also for busybox itself.
203 You need to have a working dynamic linker to use this variant.
206 bool "Build with Large File Support (for accessing files > 2 GB)"
208 select FDISK_SUPPORT_LARGE_DISKS
210 If you want to build BusyBox with large file support, then enable
211 this option. This will have no effect if your kernel or your C
212 library lacks large file support for large files. Some of the
213 programs that can benefit from large file support include dd, gzip,
214 cp, mount, tar, and many others. If you want to access files larger
215 than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'.
217 config USING_CROSS_COMPILER
218 bool "Do you want to build BusyBox with a Cross Compiler?"
221 Do you want to build BusyBox with a Cross Compiler? If so,
222 then enable this option. Otherwise leave it set to 'N'.
224 config CROSS_COMPILER_PREFIX
225 string "Cross Compiler prefix"
226 default "/usr/i386-linux-uclibc/bin/i386-uclibc-"
227 depends on USING_CROSS_COMPILER
229 If you want to build BusyBox with a cross compiler, then you
230 will need to set this to the cross-compiler prefix. For example,
231 if my cross-compiler is /usr/i386-linux-uclibc/bin/i386-uclibc-gcc
232 then I would enter '/usr/i386-linux-uclibc/bin/i386-uclibc-' here,
233 which will ensure the correct compiler is used.
235 config EXTRA_CFLAGS_OPTIONS
236 string "Any extra CFLAGS options for the compiler?"
239 Do you want to pass any extra CFLAGS options to the compiler as
240 you build BusyBox? If so, this is the option for you... For example,
241 if you want to add some simple compiler switches (like -march=i686),
242 or check for warnings using -Werror, just those options here.
244 config CONFIG_BUILD_AT_ONCE
245 bool "Compile all sources at once"
248 Normally each source-file is compiled with one invocation of
250 If you set this option, all sources are compiled at once.
251 This gives the compiler more opportunities to optimize which can
252 result in smaller and/or faster binaries.
254 Setting this option will consume alot of memory, e.g. if you
255 enable all applets with all features, gcc uses more than 300MB
256 RAM during compilation of busybox.
258 This option is most likely only beneficial for newer compilers
259 such as gcc-4.1 and above.
261 Say 'N' unless you know what you are doing.
265 menu 'Debugging Options'
268 bool "Build BusyBox with Debugging symbols"
271 Say Y here if you wish to compile BusyBox with debugging symbols.
272 This will allow you to use a debugger to examine BusyBox internals
273 while applets are running. This increases the size of the binary
274 considerably and should only be used when doing development.
275 If you are doing development and want to debug BusyBox, answer Y.
277 Most people should answer N.
280 prompt "Additional debugging library"
281 default CONFIG_NO_DEBUG_LIB
282 depends on CONFIG_DEBUG
284 Using an additional debugging library will make BusyBox become
285 considerable larger and will cause it to run more slowly. You
286 should always leave this option disabled for production use.
290 This enables compiling with dmalloc ( http://dmalloc.com/ )
291 which is an excellent public domain mem leak and malloc problem
292 detector. To enable dmalloc, before running busybox you will
293 want to properly set your environment, for example:
294 export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
295 The 'debug=' value is generated using the following command
296 dmalloc -p log-stats -p log-non-free -p log-bad-space -p log-elapsed-time \
297 -p check-fence -p check-heap -p check-lists -p check-blank \
298 -p check-funcs -p realloc-copy -p allow-free-null
300 Electric-fence support:
301 -----------------------
302 This enables compiling with Electric-fence support. Electric
303 fence is another very useful malloc debugging library which uses
304 your computer's virtual memory hardware to detect illegal memory
305 accesses. This support will make BusyBox be considerable larger
306 and run slower, so you should leave this option disabled unless
307 you are hunting a hard to find memory problem.
310 config CONFIG_NO_DEBUG_LIB
313 config CONFIG_DMALLOC
317 bool "Electric-fence"
321 config CONFIG_STRIP_BINARIES
322 bool "Strip busybox objects"
323 default y if !CONFIG_DEBUG
324 default n if CONFIG_DEBUG
326 Whether or not we strip the busybox binary and such.
328 config CONFIG_DEBUG_YANK_SUSv2
329 bool "Disable obsolete features removed before SUSv3?"
332 This option will disable backwards compatability with SuSv2,
333 specifically, old-style numeric options ('command -1 <file>')
334 will not be supported in head, tail, and fold. (Note: should
335 yank from renice too.)
339 menu 'Installation Options'
341 config CONFIG_INSTALL_NO_USR
342 bool "Don't use /usr"
345 Disable use of /usr. Don't activate this option if you don't know
346 that you really want this behaviour.
349 prompt "Applets links"
350 default CONFIG_INSTALL_APPLET_SYMLINKS
352 Choose how you install applets links.
354 config CONFIG_INSTALL_APPLET_SYMLINKS
357 Install applets as soft-links to the busybox binary. This needs some
358 free inodes on the filesystem, but might help with filesystem
359 generators that can't cope with hard-links.
361 config CONFIG_INSTALL_APPLET_HARDLINKS
364 Install applets as hard-links to the busybox binary. This might count
365 on a filesystem with few inodes.
367 config CONFIG_INSTALL_APPLET_DONT
369 prompt "not installed"
370 depends on CONFIG_FEATURE_INSTALLER || CONFIG_FEATURE_SH_STANDALONE_SHELL
372 Do not install applets links. Usefull when using the -install feature
373 or a standalone shell for rescue pruposes.
378 string "BusyBox installation prefix"
381 Define your directory to install BusyBox files/subdirs in.
385 source libbb/Config.in
391 source archival/Config.in
392 source coreutils/Config.in
393 source console-tools/Config.in
394 source debianutils/Config.in
395 source editors/Config.in
396 source findutils/Config.in
397 source init/Config.in
398 source loginutils/Config.in
399 source e2fsprogs/Config.in
400 source modutils/Config.in
401 source util-linux/Config.in
402 source miscutils/Config.in
403 source networking/Config.in
404 source procps/Config.in
405 source shell/Config.in
406 source sysklogd/Config.in