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