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