package/busybox/config/Config.in

   1 #
   2 # For a description of the syntax of this configuration file,
   3 # see scripts/kbuild/config-language.txt.
   4 #
   5
   6
   7 config BUSYBOX_CONFIG_HAVE_DOT_CONFIG
   8         bool
   9         default y
  10
  11 menu "Busybox Settings"
  12
  13 menu "General Configuration"
  14
  15 config BUSYBOX_CONFIG_DESKTOP
  16         bool "Enable options for full-blown desktop systems"
  17         default n
  18         help
  19           Enable options and features which are not essential.
  20           Select this only if you plan to use busybox on full-blown
  21           desktop machine with common Linux distro, not on an embedded box.
  22
  23 config BUSYBOX_CONFIG_FEATURE_ASSUME_UNICODE
  24         bool "Assume that 1:1 char/glyph correspondence is not true"
  25         default n
  26         help
  27           This makes various applets aware that one byte is not
  28           one character on screen.
  29
  30           Busybox aims to eventually work correctly with Unicode displays.
  31           Any older encodings are not guaranteed to work.
  32           Probably by the time when busybox will be fully Unicode-clean,
  33           other encodings will be mainly of historic interest.
  34
  35 choice
  36         prompt "Buffer allocation policy"
  37         default BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_ON_STACK
  38         help
  39           There are 3 ways BusyBox can handle buffer allocations:
  40           - Use malloc. This costs code size for the call to xmalloc.
  41           - Put them on stack. For some very small machines with limited stack
  42             space, this can be deadly.  For most folks, this works just fine.
  43           - Put them in BSS. This works beautifully for computers with a real
  44             MMU (and OS support), but wastes runtime RAM for uCLinux. This
  45             behavior was the only one available for BusyBox versions 0.48 and
  46             earlier.
  47
  48 config BUSYBOX_CONFIG_FEATURE_BUFFERS_USE_MALLOC
  49         bool "Allocate with Malloc"
  50
  51 config BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_ON_STACK
  52         bool "Allocate on the Stack"
  53
  54 config BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_IN_BSS
  55         bool "Allocate in the .bss section"
  56
  57 endchoice
  58
  59 config BUSYBOX_CONFIG_SHOW_USAGE
  60         bool "Show terse applet usage messages"
  61         default y
  62         help
  63           All BusyBox applets will show help messages when invoked with
  64           wrong arguments. You can turn off printing these terse usage
  65           messages if you say no here.
  66           This will save you up to 7k.
  67
  68 config BUSYBOX_CONFIG_FEATURE_VERBOSE_USAGE
  69         bool "Show verbose applet usage messages"
  70         default y
  71         select BUSYBOX_CONFIG_SHOW_USAGE
  72         help
  73           All BusyBox applets will show more verbose help messages when
  74           busybox is invoked with --help.  This will add a lot of text to the
  75           busybox binary.  In the default configuration, this will add about
  76           13k, but it can add much more depending on your configuration.
  77
  78 config BUSYBOX_CONFIG_FEATURE_COMPRESS_USAGE
  79         bool "Store applet usage messages in compressed form"
  80         default y
  81         depends on BUSYBOX_CONFIG_SHOW_USAGE
  82         help
  83           Store usage messages in compressed form, uncompress them on-the-fly
  84           when <applet> --help is called.
  85
  86           If you have a really tiny busybox with few applets enabled (and
  87           bunzip2 isn't one of them), the overhead of the decompressor might
  88           be noticeable.  Also, if you run executables directly from ROM
  89           and have very little memory, this might not be a win.  Otherwise,
  90           you probably want this.
  91
  92 config BUSYBOX_CONFIG_FEATURE_INSTALLER
  93         bool "Support --install [-s] to install applet links at runtime"
  94         default n
  95         help
  96           Enable 'busybox --install [-s]' support.  This will allow you to use
  97           busybox at runtime to create hard links or symlinks for all the
  98           applets that are compiled into busybox.
  99
 100 config BUSYBOX_CONFIG_LOCALE_SUPPORT
 101         bool "Enable locale support (system needs locale for this to work)"
 102         default n
 103         help
 104           Enable this if your system has locale support and you would like
 105           busybox to support locale settings.
 106
 107 config BUSYBOX_CONFIG_GETOPT_LONG
 108         bool "Support for --long-options"
 109         default y
 110         help
 111           Enable this if you want busybox applets to use the gnu --long-option
 112           style, in addition to single character -a -b -c style options.
 113
 114 config BUSYBOX_CONFIG_FEATURE_DEVPTS
 115         bool "Use the devpts filesystem for Unix98 PTYs"
 116         default y
 117         help
 118           Enable if you want BusyBox to use Unix98 PTY support. If enabled,
 119           busybox will use /dev/ptmx for the master side of the pseudoterminal
 120           and /dev/pts/<number> for the slave side.  Otherwise, BSD style
 121           /dev/ttyp<number> will be used. To use this option, you should have
 122           devpts mounted.
 123
 124 config BUSYBOX_CONFIG_FEATURE_CLEAN_UP
 125         bool "Clean up all memory before exiting (usually not needed)"
 126         default n
 127         help
 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.
 132
 133           Don't enable this unless you have a really good reason to clean
 134           things up manually.
 135
 136 config BUSYBOX_CONFIG_FEATURE_PIDFILE
 137         bool "Support writing pidfiles"
 138         default y
 139         help
 140           This option makes some applets (e.g. crond, syslogd, inetd) write
 141           a pidfile in /var/run. Some applications rely on them.
 142
 143 config BUSYBOX_CONFIG_FEATURE_SUID
 144         bool "Support for SUID/SGID handling"
 145         default y
 146         help
 147           With this option you can install the busybox binary belonging
 148           to root with the suid bit set, and it'll and it'll automatically drop
 149           priviledges for applets that don't need root access.
 150
 151           If you're really paranoid and don't want to do this, build two
 152           busybox binaries with different applets in them (and the appropriate
 153           symlinks pointing to each binary), and only set the suid bit on the
 154           one that needs it.  The applets currently marked to need the suid bit
 155           are login, passwd, su, ping, traceroute, crontab, dnsd, ipcrm, ipcs,
 156           and vlock.
 157
 158 config BUSYBOX_CONFIG_FEATURE_SUID_CONFIG
 159         bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
 160         default n if BUSYBOX_CONFIG_FEATURE_SUID
 161         depends on BUSYBOX_CONFIG_FEATURE_SUID
 162         help
 163           Allow the SUID / SGID state of an applet to be determined at runtime
 164           by checking /etc/busybox.conf.  (This is sort of a poor man's sudo.)
 165           The format of this file is as follows:
 166
 167           <applet> = [Ssx-][Ssx-][x-] (<username>|<uid>).(<groupname>|<gid>)
 168
 169           An example might help:
 170
 171           [SUID]
 172           su = ssx root.0 # applet su can be run by anyone and runs with euid=0/egid=0
 173           su = ssx        # exactly the same
 174
 175           mount = sx- root.disk # applet mount can be run by root and members of group disk
 176                                 # and runs with euid=0
 177
 178           cp = --- # disable applet cp for everyone
 179
 180           The file has to be owned by user root, group root and has to be
 181           writeable only by root:
 182                 (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf)
 183           The busybox executable has to be owned by user root, group
 184           root and has to be setuid root for this to work:
 185                 (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox)
 186
 187           Robert 'sandman' Griebl has more information here:
 188           <url: http://www.softforge.de/bb/suid.html >.
 189
 190 config BUSYBOX_CONFIG_FEATURE_SUID_CONFIG_QUIET
 191         bool "Suppress warning message if /etc/busybox.conf is not readable"
 192         default n
 193         depends on BUSYBOX_CONFIG_FEATURE_SUID_CONFIG
 194         help
 195           /etc/busybox.conf should be readable by the user needing the SUID, check
 196           this option to avoid users to be notified about missing permissions.
 197
 198 config BUSYBOX_CONFIG_SELINUX
 199         bool "Support NSA Security Enhanced Linux"
 200         default n
 201         help
 202           Enable support for SELinux in applets ls, ps, and id.  Also provide
 203           the option of compiling in SELinux applets.
 204
 205           If you do not have a complete SELinux userland installed, this stuff
 206           will not compile. Go visit
 207                 http://www.nsa.gov/selinux/index.html
 208           to download the necessary stuff to allow busybox to compile with
 209           this option enabled. Specifially, libselinux 1.28 or better is
 210           directly required by busybox. If the installation is located in a
 211           non-standard directory, provide it by invoking make as follows:
 212                 CFLAGS=-I<libselinux-include-path> \
 213                 LDFLAGS=-L<libselinux-lib-path> \
 214                 make
 215
 216           Most people will leave this set to 'N'.
 217
 218 config BUSYBOX_CONFIG_FEATURE_PREFER_APPLETS
 219         bool "exec prefers applets"
 220         default y
 221         help
 222           This is an experimental option which directs applets about to
 223           call 'exec' to try and find an applicable busybox applet before
 224           searching the PATH. This is typically done by exec'ing
 225           /proc/self/exe.
 226           This may affect shell, find -exec, xargs and similar applets.
 227           They will use applets even if /bin/<applet> -> busybox link
 228           is missing (or is not a link to busybox). However, this causes
 229           problems in chroot jails without mounted /proc and with ps/top
 230           (command name can be shown as 'exe' for applets started this way).
 231
 232 config BUSYBOX_CONFIG_BUSYBOX_EXEC_PATH
 233         string "Path to BusyBox executable"
 234         default "/proc/self/exe"
 235         help
 236           When Busybox applets need to run other busybox applets, BusyBox
 237           sometimes needs to exec() itself.  When the /proc filesystem is
 238           mounted, /proc/self/exe always points to the currently running
 239           executable.  If you haven't got /proc, set this to wherever you
 240           want to run BusyBox from.
 241
 242 # These are auto-selected by other options
 243
 244 config BUSYBOX_CONFIG_FEATURE_SYSLOG
 245         bool "Support for logging to syslog"
 246         default y
 247         help
 248           This option is auto-selected when you select any applet which may
 249           send its output to syslog. You do not need to select it manually.
 250
 251 config BUSYBOX_CONFIG_FEATURE_HAVE_RPC
 252         bool "RPC support"
 253         default y
 254         help
 255           This is automatically selected if any of enabled applets need it.
 256           You do not need to select it manually.
 257
 258 endmenu
 259
 260 menu 'Build Options'
 261
 262 config BUSYBOX_CONFIG_STATIC
 263         bool "Build BusyBox as a static binary (no shared libs)"
 264         default n
 265         help
 266           If you want to build a static BusyBox binary, which does not
 267           use or require any shared libraries, then enable this option.
 268           This can cause BusyBox to be considerably larger, so you should
 269           leave this option false unless you have a good reason (i.e.
 270           your target platform does not support shared libraries, or
 271           you are building an initrd which doesn't need anything but
 272           BusyBox, etc).
 273
 274           Most people will leave this set to 'N'.
 275
 276 config BUSYBOX_CONFIG_PIE
 277         bool "Build BusyBox as a position independent executable"
 278         default n
 279         depends on !BUSYBOX_CONFIG_STATIC
 280         help
 281           (TODO: what is it and why/when is it useful?)
 282           Most people will leave this set to 'N'.
 283
 284 config BUSYBOX_CONFIG_NOMMU
 285         bool "Force NOMMU build"
 286         default n
 287         help
 288           Busybox tries to detect whether architecture it is being
 289           built against supports MMU or not. If this detection fails,
 290           or if you want to build NOMMU version of busybox for testing,
 291           you may force NOMMU build here.
 292
 293           Most people will leave this set to 'N'.
 294
 295 # PIE can be made to work with BUILD_LIBBUSYBOX, but currently
 296 # build system does not support that
 297 config BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 298         bool "Build shared libbusybox"
 299         default n
 300         depends on !BUSYBOX_CONFIG_FEATURE_PREFER_APPLETS && !BUSYBOX_CONFIG_PIE && !BUSYBOX_CONFIG_STATIC
 301         help
 302           Build a shared library libbusybox.so.N.N.N which contains all
 303           busybox code.
 304
 305           This feature allows every applet to be built as a tiny
 306           separate executable.  Enabling it for "one big busybox binary"
 307           approach serves no purpose and increases code size.
 308           You should almost certainly say "no" to this.
 309
 310 ### config FEATURE_FULL_LIBBUSYBOX
 311 ###     bool "Feature-complete libbusybox"
 312 ###     default n if !FEATURE_SHARED_BUSYBOX
 313 ###     depends on BUILD_LIBBUSYBOX
 314 ###     help
 315 ###       Build a libbusybox with the complete feature-set, disregarding
 316 ###       the actually selected config.
 317 ###
 318 ###       Normally, libbusybox will only contain the features which are
 319 ###       used by busybox itself. If you plan to write a separate
 320 ###       standalone application which uses libbusybox say 'Y'.
 321 ###
 322 ###       Note: libbusybox is GPL, not LGPL, and exports no stable API that
 323 ###       might act as a copyright barrier.  We can and will modify the
 324 ###       exported function set between releases (even minor version number
 325 ###       changes), and happily break out-of-tree features.
 326 ###
 327 ###       Say 'N' if in doubt.
 328
 329 config BUSYBOX_CONFIG_FEATURE_INDIVIDUAL
 330         bool "Produce a binary for each applet, linked against libbusybox"
 331         default n
 332         depends on !BUSYBOX_CONFIG_STATIC && BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 333         help
 334           If your CPU architecture doesn't allow for sharing text/rodata
 335           sections of running binaries, but allows for runtime dynamic
 336           libraries, this option will allow you to reduce memory footprint
 337           when you have many different applets running at once.
 338
 339           If your CPU architecture allows for sharing text/rodata,
 340           having single binary is more optimal.
 341
 342           Each applet will be a tiny program, dynamically linked
 343           against libbusybox.so.N.N.N.
 344
 345           You need to have a working dynamic linker.
 346
 347 config BUSYBOX_CONFIG_FEATURE_SHARED_BUSYBOX
 348         bool "Produce additional busybox binary linked against libbusybox"
 349         default n
 350         depends on !BUSYBOX_CONFIG_STATIC && BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 351         help
 352           Build busybox, dynamically linked against libbusybox.so.N.N.N.
 353
 354           You need to have a working dynamic linker.
 355
 356 ### config BUILD_AT_ONCE
 357 ###     bool "Compile all sources at once"
 358 ###     default n
 359 ###     help
 360 ###       Normally each source-file is compiled with one invocation of
 361 ###       the compiler.
 362 ###       If you set this option, all sources are compiled at once.
 363 ###       This gives the compiler more opportunities to optimize which can
 364 ###       result in smaller and/or faster binaries.
 365 ###
 366 ###       Setting this option will consume alot of memory, e.g. if you
 367 ###       enable all applets with all features, gcc uses more than 300MB
 368 ###       RAM during compilation of busybox.
 369 ###
 370 ###       This option is most likely only beneficial for newer compilers
 371 ###       such as gcc-4.1 and above.
 372 ###
 373 ###       Say 'N' unless you know what you are doing.
 374
 375 config BUSYBOX_CONFIG_LFS
 376         bool
 377         default y
 378         select BUSYBOX_CONFIG_FDISK_SUPPORT_LARGE_DISKS
 379         help
 380           If you want to build BusyBox with large file support, then enable
 381           this option.  This will have no effect if your kernel or your C
 382           library lacks large file support for large files.  Some of the
 383           programs that can benefit from large file support include dd, gzip,
 384           cp, mount, tar, and many others.  If you want to access files larger
 385           than 2 Gigabytes, enable this option.  Otherwise, leave it set to 'N'.
 386
 387 config BUSYBOX_CONFIG_CROSS_COMPILER_PREFIX
 388         string "Cross Compiler prefix"
 389         default ""
 390         help
 391           If you want to build BusyBox with a cross compiler, then you
 392           will need to set this to the cross-compiler prefix, for example,
 393           "i386-uclibc-". Note that CROSS_COMPILE environment variable
 394           or "make CROSS_COMPILE=xxx ..." will override this selection.
 395           For native build leave it empty.
 396
 397 endmenu
 398
 399 menu 'Debugging Options'
 400
 401 config BUSYBOX_CONFIG_DEBUG
 402         bool "Build BusyBox with extra Debugging symbols"
 403         default n
 404         help
 405           Say Y here if you wish to examine BusyBox internals while applets are
 406           running.  This increases the size of the binary considerably, and
 407           should only be used when doing development.  If you are doing
 408           development and want to debug BusyBox, answer Y.
 409
 410           Most people should answer N.
 411
 412 config BUSYBOX_CONFIG_DEBUG_PESSIMIZE
 413         bool "Disable compiler optimizations."
 414         default n
 415         depends on BUSYBOX_CONFIG_DEBUG
 416         help
 417           The compiler's optimization of source code can eliminate and reorder
 418           code, resulting in an executable that's hard to understand when
 419           stepping through it with a debugger.  This switches it off, resulting
 420           in a much bigger executable that more closely matches the source
 421           code.
 422
 423 config BUSYBOX_CONFIG_WERROR
 424         bool "Abort compilation on any warning"
 425         default n
 426         help
 427           Selecting this will add -Werror to gcc command line.
 428
 429           Most people should answer N.
 430
 431 choice
 432         prompt "Additional debugging library"
 433         default BUSYBOX_CONFIG_NO_DEBUG_LIB
 434         help
 435           Using an additional debugging library will make BusyBox become
 436           considerable larger and will cause it to run more slowly.  You
 437           should always leave this option disabled for production use.
 438
 439           dmalloc support:
 440           ----------------
 441           This enables compiling with dmalloc ( http://dmalloc.com/ )
 442           which is an excellent public domain mem leak and malloc problem
 443           detector.  To enable dmalloc, before running busybox you will
 444           want to properly set your environment, for example:
 445             export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
 446           The 'debug=' value is generated using the following command
 447             dmalloc -p log-stats -p log-non-free -p log-bad-space -p log-elapsed-time \
 448                -p check-fence -p check-heap -p check-lists -p check-blank \
 449                -p check-funcs -p realloc-copy -p allow-free-null
 450
 451           Electric-fence support:
 452           -----------------------
 453           This enables compiling with Electric-fence support.  Electric
 454           fence is another very useful malloc debugging library which uses
 455           your computer's virtual memory hardware to detect illegal memory
 456           accesses.  This support will make BusyBox be considerable larger
 457           and run slower, so you should leave this option disabled unless
 458           you are hunting a hard to find memory problem.
 459
 460
 461 config BUSYBOX_CONFIG_NO_DEBUG_LIB
 462         bool "None"
 463
 464 config BUSYBOX_CONFIG_DMALLOC
 465         bool "Dmalloc"
 466
 467 config BUSYBOX_CONFIG_EFENCE
 468         bool "Electric-fence"
 469
 470 endchoice
 471
 472 config BUSYBOX_CONFIG_INCLUDE_SUSv2
 473         bool "Enable obsolete features removed before SUSv3?"
 474         default y
 475         help
 476           This option will enable backwards compatibility with SuSv2,
 477           specifically, old-style numeric options ('command -1 <file>')
 478           will be supported in head, tail, and fold.  (Note: should
 479           affect renice too.)
 480
 481 endmenu
 482
 483 menu 'Installation Options'
 484
 485 config BUSYBOX_CONFIG_INSTALL_NO_USR
 486         bool "Don't use /usr"
 487         default n
 488         help
 489           Disable use of /usr. Don't activate this option if you don't know
 490           that you really want this behaviour.
 491
 492 choice
 493         prompt "Applets links"
 494         default BUSYBOX_CONFIG_INSTALL_APPLET_SYMLINKS
 495         help
 496           Choose how you install applets links.
 497
 498 config BUSYBOX_CONFIG_INSTALL_APPLET_SYMLINKS
 499         bool "as soft-links"
 500         help
 501           Install applets as soft-links to the busybox binary. This needs some
 502           free inodes on the filesystem, but might help with filesystem
 503           generators that can't cope with hard-links.
 504
 505 config BUSYBOX_CONFIG_INSTALL_APPLET_HARDLINKS
 506         bool "as hard-links"
 507         help
 508           Install applets as hard-links to the busybox binary. This might count
 509           on a filesystem with few inodes.
 510
 511 config BUSYBOX_CONFIG_INSTALL_APPLET_SCRIPT_WRAPPERS
 512         bool "as script wrappers"
 513         help
 514           Install applets as script wrappers that call the busybox binary.
 515
 516 config BUSYBOX_CONFIG_INSTALL_APPLET_DONT
 517         bool "not installed"
 518         depends on BUSYBOX_CONFIG_FEATURE_INSTALLER || BUSYBOX_CONFIG_FEATURE_SH_STANDALONE || BUSYBOX_CONFIG_FEATURE_PREFER_APPLETS
 519         help
 520           Do not install applet links. Useful when using the -install feature
 521           or a standalone shell for rescue purposes.
 522
 523 endchoice
 524
 525 choice
 526         prompt "/bin/sh applet link"
 527         default BUSYBOX_CONFIG_INSTALL_SH_APPLET_SYMLINK
 528         depends on BUSYBOX_CONFIG_INSTALL_APPLET_SCRIPT_WRAPPERS
 529         help
 530           Choose how you install /bin/sh applet link.
 531
 532 config BUSYBOX_CONFIG_INSTALL_SH_APPLET_SYMLINK
 533         bool "as soft-link"
 534         help
 535           Install /bin/sh applet as soft-link to the busybox binary.
 536
 537 config BUSYBOX_CONFIG_INSTALL_SH_APPLET_HARDLINK
 538         bool "as hard-link"
 539         help
 540           Install /bin/sh applet as hard-link to the busybox binary.
 541
 542 config BUSYBOX_CONFIG_INSTALL_SH_APPLET_SCRIPT_WRAPPER
 543         bool "as script wrapper"
 544         help
 545           Install /bin/sh applet as script wrapper that call the busybox binary.
 546
 547 endchoice
 548
 549 config BUSYBOX_CONFIG_PREFIX
 550         string "BusyBox installation prefix"
 551         default "./_install"
 552         help
 553           Define your directory to install BusyBox files/subdirs in.
 554
 555 endmenu
 556
 557 source package/busybox/config/libbb/Config.in
 558
 559 endmenu
 560
 561 comment "Applets"
 562
 563 source package/busybox/config/archival/Config.in
 564 source package/busybox/config/coreutils/Config.in
 565 source package/busybox/config/console-tools/Config.in
 566 source package/busybox/config/debianutils/Config.in
 567 source package/busybox/config/editors/Config.in
 568 source package/busybox/config/findutils/Config.in
 569 source package/busybox/config/init/Config.in
 570 source package/busybox/config/loginutils/Config.in
 571 source package/busybox/config/e2fsprogs/Config.in
 572 source package/busybox/config/modutils/Config.in
 573 source package/busybox/config/util-linux/Config.in
 574 source package/busybox/config/miscutils/Config.in
 575 source package/busybox/config/networking/Config.in
 576 source package/busybox/config/procps/Config.in
 577 source package/busybox/config/shell/Config.in
 578 source package/busybox/config/sysklogd/Config.in
 579 source package/busybox/config/runit/Config.in
 580 source package/busybox/config/selinux/Config.in
 581 source package/busybox/config/printutils/Config.in