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_INCLUDE_SUSv2
  33         bool "Enable obsolete features removed before SUSv3"
  34         default y
  35         help
  36           This option will enable backwards compatibility with SuSv2,
  37           specifically, old-style numeric options ('command -1 <file>')
  38           will be supported in head, tail, and fold. (Note: should
  39           affect renice too.)
  40
  41 config BUSYBOX_CONFIG_USE_PORTABLE_CODE
  42         bool "Avoid using GCC-specific code constructs"
  43         default n
  44         help
  45           Use this option if you are trying to compile busybox with
  46           compiler other than gcc.
  47           If you do use gcc, this option may needlessly increase code size.
  48
  49 choice
  50         prompt "Buffer allocation policy"
  51         default BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_ON_STACK
  52         help
  53           There are 3 ways BusyBox can handle buffer allocations:
  54           - Use malloc. This costs code size for the call to xmalloc.
  55           - Put them on stack. For some very small machines with limited stack
  56             space, this can be deadly. For most folks, this works just fine.
  57           - Put them in BSS. This works beautifully for computers with a real
  58             MMU (and OS support), but wastes runtime RAM for uCLinux. This
  59             behavior was the only one available for BusyBox versions 0.48 and
  60             earlier.
  61
  62 config BUSYBOX_CONFIG_FEATURE_BUFFERS_USE_MALLOC
  63         bool "Allocate with Malloc"
  64
  65 config BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_ON_STACK
  66         bool "Allocate on the Stack"
  67
  68 config BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_IN_BSS
  69         bool "Allocate in the .bss section"
  70
  71 endchoice
  72
  73 config BUSYBOX_CONFIG_SHOW_USAGE
  74         bool "Show terse applet usage messages"
  75         default y
  76         help
  77           All BusyBox applets will show help messages when invoked with
  78           wrong arguments. You can turn off printing these terse usage
  79           messages if you say no here.
  80           This will save you up to 7k.
  81
  82 config BUSYBOX_CONFIG_FEATURE_VERBOSE_USAGE
  83         bool "Show verbose applet usage messages"
  84         default y
  85         depends on BUSYBOX_CONFIG_SHOW_USAGE
  86         help
  87           All BusyBox applets will show more verbose help messages when
  88           busybox is invoked with --help. This will add a lot of text to the
  89           busybox binary. In the default configuration, this will add about
  90           13k, but it can add much more depending on your configuration.
  91
  92 config BUSYBOX_CONFIG_FEATURE_COMPRESS_USAGE
  93         bool "Store applet usage messages in compressed form"
  94         default y
  95         depends on BUSYBOX_CONFIG_SHOW_USAGE
  96         help
  97           Store usage messages in compressed form, uncompress them on-the-fly
  98           when <applet> --help is called.
  99
 100           If you have a really tiny busybox with few applets enabled (and
 101           bunzip2 isn't one of them), the overhead of the decompressor might
 102           be noticeable. Also, if you run executables directly from ROM
 103           and have very little memory, this might not be a win. Otherwise,
 104           you probably want this.
 105
 106 config BUSYBOX_CONFIG_FEATURE_INSTALLER
 107         bool "Support --install [-s] to install applet links at runtime"
 108         default n
 109         help
 110           Enable 'busybox --install [-s]' support. This will allow you to use
 111           busybox at runtime to create hard links or symlinks for all the
 112           applets that are compiled into busybox.
 113
 114 config BUSYBOX_CONFIG_LOCALE_SUPPORT
 115         bool "Enable locale support (system needs locale for this to work)"
 116         default n
 117         help
 118           Enable this if your system has locale support and you would like
 119           busybox to support locale settings.
 120
 121 config BUSYBOX_CONFIG_UNICODE_SUPPORT
 122         bool "Support Unicode"
 123         default n
 124         help
 125           This makes various applets aware that one byte is not
 126           one character on screen.
 127
 128           Busybox aims to eventually work correctly with Unicode displays.
 129           Any older encodings are not guaranteed to work.
 130           Probably by the time when busybox will be fully Unicode-clean,
 131           other encodings will be mainly of historic interest.
 132
 133 config BUSYBOX_CONFIG_UNICODE_USING_LOCALE
 134         bool "Use libc routines for Unicode (else uses internal ones)"
 135         default n
 136         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT && BUSYBOX_CONFIG_LOCALE_SUPPORT
 137         help
 138           With this option on, Unicode support is implemented using libc
 139           routines. Otherwise, internal implementation is used.
 140
 141 config BUSYBOX_CONFIG_FEATURE_CHECK_UNICODE_IN_ENV
 142         bool "Check $LANG environment variable"
 143         default n
 144         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT && !BUSYBOX_CONFIG_UNICODE_USING_LOCALE
 145         help
 146           With this option on, Unicode support is activated
 147           only if LANG variable has the value of the form "xxxx.utf8"
 148
 149           Otherwise, Unicode support will be always enabled and active.
 150
 151 config BUSYBOX_CONFIG_SUBST_WCHAR
 152         int "Character code to substitute unprintable characters with"
 153         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT
 154         default 63
 155         help
 156           Typical values are 63 for '?' (works with any output device),
 157           30 for ASCII substitute control code,
 158           65533 (0xfffd) for Unicode replacement character.
 159
 160 config BUSYBOX_CONFIG_LAST_SUPPORTED_WCHAR
 161         int "Range of supported Unicode characters"
 162         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT
 163         default 767
 164         help
 165           Any character with Unicode value bigger than this is assumed
 166           to be non-printable on output device. Many applets replace
 167           such chars with substitution character.
 168
 169           The idea is that many valid printable Unicode chars are
 170           nevertheless are not displayed correctly. Think about
 171           combining charachers, double-wide hieroglyphs, obscure
 172           characters in dozens of ancient scripts...
 173           Many terminals, terminal emulators, xterms etc will fail
 174           to handle them correctly. Choose the smallest value
 175           which suits your needs.
 176
 177           Typical values are:
 178           126 - ASCII only
 179           767 (0x2ff) - there are no combining chars in [0..767] range
 180                         (the range includes Latin 1, Latin Ext. A and B),
 181                         code is ~700 bytes smaller for this case.
 182           4351 (0x10ff) - there are no double-wide chars in [0..4351] range,
 183                         code is ~300 bytes smaller for this case.
 184           12799 (0x31ff) - nearly all non-ideographic characters are
 185                         available in [0..12799] range, including
 186                         East Asian scripts like katakana, hiragana, hangul,
 187                         bopomofo...
 188           0 - off, any valid printable Unicode character will be printed.
 189
 190 config BUSYBOX_CONFIG_UNICODE_COMBINING_WCHARS
 191         bool "Allow zero-width Unicode characters on output"
 192         default n
 193         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT
 194         help
 195           With this option off, any Unicode char with width of 0
 196           is substituted on output.
 197
 198 config BUSYBOX_CONFIG_UNICODE_WIDE_WCHARS
 199         bool "Allow wide Unicode characters on output"
 200         default n
 201         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT
 202         help
 203           With this option off, any Unicode char with width > 1
 204           is substituted on output.
 205
 206 config BUSYBOX_CONFIG_UNICODE_BIDI_SUPPORT
 207         bool "Bidirectional character-aware line input"
 208         default n
 209         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT && !BUSYBOX_CONFIG_UNICODE_USING_LOCALE
 210         help
 211           With this option on, right-to-left Unicode characters
 212           are treated differently on input (e.g. cursor movement).
 213
 214 config BUSYBOX_CONFIG_UNICODE_NEUTRAL_TABLE
 215         bool "In bidi input, support non-ASCII neutral chars too"
 216         default n
 217         depends on BUSYBOX_CONFIG_UNICODE_BIDI_SUPPORT
 218         help
 219           In most cases it's enough to treat only ASCII non-letters
 220           (i.e. punctuation, numbers and space) as characters
 221           with neutral directionality.
 222           With this option on, more extensive (and bigger) table
 223           of neutral chars will be used.
 224
 225 config BUSYBOX_CONFIG_UNICODE_PRESERVE_BROKEN
 226         bool "Make it possible to enter sequences of chars which are not Unicode"
 227         default n
 228         depends on BUSYBOX_CONFIG_UNICODE_SUPPORT
 229         help
 230           With this option on, invalid UTF-8 bytes are not substituted
 231           with the selected substitution character.
 232           For example, this means that entering 'l', 's', ' ', 0xff, [Enter]
 233           at shell prompt will list file named 0xff (single char name
 234           with char value 255), not file named '?'.
 235
 236 config BUSYBOX_CONFIG_LONG_OPTS
 237         bool "Support for --long-options"
 238         default y
 239         help
 240           Enable this if you want busybox applets to use the gnu --long-option
 241           style, in addition to single character -a -b -c style options.
 242
 243 config BUSYBOX_CONFIG_FEATURE_DEVPTS
 244         bool "Use the devpts filesystem for Unix98 PTYs"
 245         default y
 246         help
 247           Enable if you want BusyBox to use Unix98 PTY support. If enabled,
 248           busybox will use /dev/ptmx for the master side of the pseudoterminal
 249           and /dev/pts/<number> for the slave side. Otherwise, BSD style
 250           /dev/ttyp<number> will be used. To use this option, you should have
 251           devpts mounted.
 252
 253 config BUSYBOX_CONFIG_FEATURE_CLEAN_UP
 254         bool "Clean up all memory before exiting (usually not needed)"
 255         default n
 256         help
 257           As a size optimization, busybox normally exits without explicitly
 258           freeing dynamically allocated memory or closing files. This saves
 259           space since the OS will clean up for us, but it can confuse debuggers
 260           like valgrind, which report tons of memory and resource leaks.
 261
 262           Don't enable this unless you have a really good reason to clean
 263           things up manually.
 264
 265 config BUSYBOX_CONFIG_FEATURE_UTMP
 266         bool "Support utmp file"
 267         default n
 268         help
 269           The file /var/run/utmp is used to track who is currently logged in.
 270           With this option on, certain applets (getty, login, telnetd etc)
 271           will create and delete entries there.
 272           "who" applet requires this option.
 273
 274 config BUSYBOX_CONFIG_FEATURE_WTMP
 275         bool "Support wtmp file"
 276         default n
 277         select BUSYBOX_CONFIG_FEATURE_UTMP
 278         help
 279           The file /var/run/wtmp is used to track when users have logged into
 280           and logged out of the system.
 281           With this option on, certain applets (getty, login, telnetd etc)
 282           will append new entries there.
 283           "last" applet requires this option.
 284
 285 config BUSYBOX_CONFIG_FEATURE_PIDFILE
 286         bool "Support writing pidfiles"
 287         default y
 288         help
 289           This option makes some applets (e.g. crond, syslogd, inetd) write
 290           a pidfile in /var/run. Some applications rely on them.
 291
 292 config BUSYBOX_CONFIG_FEATURE_SUID
 293         bool "Support for SUID/SGID handling"
 294         default y
 295         help
 296           With this option you can install the busybox binary belonging
 297           to root with the suid bit set, and it will automatically drop
 298           priviledges for applets that don't need root access.
 299
 300           If you are really paranoid and don't want to do this, build two
 301           busybox binaries with different applets in them (and the appropriate
 302           symlinks pointing to each binary), and only set the suid bit on the
 303           one that needs it. The applets currently marked to need the suid bit
 304           are:
 305
 306           crontab, dnsd, findfs, ipcrm, ipcs, login, passwd, ping, su,
 307           traceroute, vlock.
 308
 309 config BUSYBOX_CONFIG_FEATURE_SUID_CONFIG
 310         bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
 311         default n if BUSYBOX_CONFIG_FEATURE_SUID
 312         depends on BUSYBOX_CONFIG_FEATURE_SUID
 313         help
 314           Allow the SUID / SGID state of an applet to be determined at runtime
 315           by checking /etc/busybox.conf. (This is sort of a poor man's sudo.)
 316           The format of this file is as follows:
 317
 318           <applet> = [Ssx-][Ssx-][x-] (<username>|<uid>).(<groupname>|<gid>)
 319
 320           An example might help:
 321
 322           [SUID]
 323           su = ssx root.0 # applet su can be run by anyone and runs with
 324                           # euid=0/egid=0
 325           su = ssx        # exactly the same
 326
 327           mount = sx- root.disk # applet mount can be run by root and members
 328                                 # of group disk and runs with euid=0
 329
 330           cp = --- # disable applet cp for everyone
 331
 332           The file has to be owned by user root, group root and has to be
 333           writeable only by root:
 334                 (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf)
 335           The busybox executable has to be owned by user root, group
 336           root and has to be setuid root for this to work:
 337                 (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox)
 338
 339           Robert 'sandman' Griebl has more information here:
 340           <url: http://www.softforge.de/bb/suid.html >.
 341
 342 config BUSYBOX_CONFIG_FEATURE_SUID_CONFIG_QUIET
 343         bool "Suppress warning message if /etc/busybox.conf is not readable"
 344         default n
 345         depends on BUSYBOX_CONFIG_FEATURE_SUID_CONFIG
 346         help
 347           /etc/busybox.conf should be readable by the user needing the SUID,
 348           check this option to avoid users to be notified about missing
 349           permissions.
 350
 351 config BUSYBOX_CONFIG_SELINUX
 352         bool "Support NSA Security Enhanced Linux"
 353         default n
 354         help
 355           Enable support for SELinux in applets ls, ps, and id. Also provide
 356           the option of compiling in SELinux applets.
 357
 358           If you do not have a complete SELinux userland installed, this stuff
 359           will not compile. Go visit
 360                 http://www.nsa.gov/selinux/index.html
 361           to download the necessary stuff to allow busybox to compile with
 362           this option enabled. Specifially, libselinux 1.28 or better is
 363           directly required by busybox. If the installation is located in a
 364           non-standard directory, provide it by invoking make as follows:
 365                 CFLAGS=-I<libselinux-include-path> \
 366                 LDFLAGS=-L<libselinux-lib-path> \
 367                 make
 368
 369           Most people will leave this set to 'N'.
 370
 371 config BUSYBOX_CONFIG_FEATURE_PREFER_APPLETS
 372         bool "exec prefers applets"
 373         default y
 374         help
 375           This is an experimental option which directs applets about to
 376           call 'exec' to try and find an applicable busybox applet before
 377           searching the PATH. This is typically done by exec'ing
 378           /proc/self/exe.
 379           This may affect shell, find -exec, xargs and similar applets.
 380           They will use applets even if /bin/<applet> -> busybox link
 381           is missing (or is not a link to busybox). However, this causes
 382           problems in chroot jails without mounted /proc and with ps/top
 383           (command name can be shown as 'exe' for applets started this way).
 384
 385 config BUSYBOX_CONFIG_BUSYBOX_EXEC_PATH
 386         string "Path to BusyBox executable"
 387         default "/proc/self/exe"
 388         help
 389           When Busybox applets need to run other busybox applets, BusyBox
 390           sometimes needs to exec() itself. When the /proc filesystem is
 391           mounted, /proc/self/exe always points to the currently running
 392           executable. If you haven't got /proc, set this to wherever you
 393           want to run BusyBox from.
 394
 395 # These are auto-selected by other options
 396
 397 config BUSYBOX_CONFIG_FEATURE_SYSLOG
 398         bool #No description makes it a hidden option
 399         default y
 400         #help
 401         #  This option is auto-selected when you select any applet which may
 402         #  send its output to syslog. You do not need to select it manually.
 403
 404 config BUSYBOX_CONFIG_FEATURE_HAVE_RPC
 405         bool #No description makes it a hidden option
 406         default y
 407         #help
 408         #  This is automatically selected if any of enabled applets need it.
 409         #  You do not need to select it manually.
 410
 411 endmenu
 412
 413 menu 'Build Options'
 414
 415 config BUSYBOX_CONFIG_STATIC
 416         bool "Build BusyBox as a static binary (no shared libs)"
 417         default n
 418         help
 419           If you want to build a static BusyBox binary, which does not
 420           use or require any shared libraries, then enable this option.
 421           This can cause BusyBox to be considerably larger, so you should
 422           leave this option false unless you have a good reason (i.e.
 423           your target platform does not support shared libraries, or
 424           you are building an initrd which doesn't need anything but
 425           BusyBox, etc).
 426
 427           Most people will leave this set to 'N'.
 428
 429 config BUSYBOX_CONFIG_PIE
 430         bool "Build BusyBox as a position independent executable"
 431         default n
 432         depends on !BUSYBOX_CONFIG_STATIC
 433         help
 434           (TODO: what is it and why/when is it useful?)
 435           Most people will leave this set to 'N'.
 436
 437 config BUSYBOX_CONFIG_NOMMU
 438         bool "Force NOMMU build"
 439         default n
 440         help
 441           Busybox tries to detect whether architecture it is being
 442           built against supports MMU or not. If this detection fails,
 443           or if you want to build NOMMU version of busybox for testing,
 444           you may force NOMMU build here.
 445
 446           Most people will leave this set to 'N'.
 447
 448 # PIE can be made to work with BUILD_LIBBUSYBOX, but currently
 449 # build system does not support that
 450 config BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 451         bool "Build shared libbusybox"
 452         default n
 453         depends on !BUSYBOX_CONFIG_FEATURE_PREFER_APPLETS && !BUSYBOX_CONFIG_PIE && !BUSYBOX_CONFIG_STATIC
 454         help
 455           Build a shared library libbusybox.so.N.N.N which contains all
 456           busybox code.
 457
 458           This feature allows every applet to be built as a tiny
 459           separate executable. Enabling it for "one big busybox binary"
 460           approach serves no purpose and increases code size.
 461           You should almost certainly say "no" to this.
 462
 463 ### config FEATURE_FULL_LIBBUSYBOX
 464 ###     bool "Feature-complete libbusybox"
 465 ###     default n if !FEATURE_SHARED_BUSYBOX
 466 ###     depends on BUILD_LIBBUSYBOX
 467 ###     help
 468 ###       Build a libbusybox with the complete feature-set, disregarding
 469 ###       the actually selected config.
 470 ###
 471 ###       Normally, libbusybox will only contain the features which are
 472 ###       used by busybox itself. If you plan to write a separate
 473 ###       standalone application which uses libbusybox say 'Y'.
 474 ###
 475 ###       Note: libbusybox is GPL, not LGPL, and exports no stable API that
 476 ###       might act as a copyright barrier. We can and will modify the
 477 ###       exported function set between releases (even minor version number
 478 ###       changes), and happily break out-of-tree features.
 479 ###
 480 ###       Say 'N' if in doubt.
 481
 482 config BUSYBOX_CONFIG_FEATURE_INDIVIDUAL
 483         bool "Produce a binary for each applet, linked against libbusybox"
 484         default n
 485         depends on BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 486         help
 487           If your CPU architecture doesn't allow for sharing text/rodata
 488           sections of running binaries, but allows for runtime dynamic
 489           libraries, this option will allow you to reduce memory footprint
 490           when you have many different applets running at once.
 491
 492           If your CPU architecture allows for sharing text/rodata,
 493           having single binary is more optimal.
 494
 495           Each applet will be a tiny program, dynamically linked
 496           against libbusybox.so.N.N.N.
 497
 498           You need to have a working dynamic linker.
 499
 500 config BUSYBOX_CONFIG_FEATURE_SHARED_BUSYBOX
 501         bool "Produce additional busybox binary linked against libbusybox"
 502         default n
 503         depends on BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 504         help
 505           Build busybox, dynamically linked against libbusybox.so.N.N.N.
 506
 507           You need to have a working dynamic linker.
 508
 509 ### config BUILD_AT_ONCE
 510 ###     bool "Compile all sources at once"
 511 ###     default n
 512 ###     help
 513 ###       Normally each source-file is compiled with one invocation of
 514 ###       the compiler.
 515 ###       If you set this option, all sources are compiled at once.
 516 ###       This gives the compiler more opportunities to optimize which can
 517 ###       result in smaller and/or faster binaries.
 518 ###
 519 ###       Setting this option will consume alot of memory, e.g. if you
 520 ###       enable all applets with all features, gcc uses more than 300MB
 521 ###       RAM during compilation of busybox.
 522 ###
 523 ###       This option is most likely only beneficial for newer compilers
 524 ###       such as gcc-4.1 and above.
 525 ###
 526 ###       Say 'N' unless you know what you are doing.
 527
 528 config BUSYBOX_CONFIG_LFS
 529         bool
 530         default y
 531         select BUSYBOX_CONFIG_FDISK_SUPPORT_LARGE_DISKS
 532         help
 533           If you want to build BusyBox with large file support, then enable
 534           this option. This will have no effect if your kernel or your C
 535           library lacks large file support for large files. Some of the
 536           programs that can benefit from large file support include dd, gzip,
 537           cp, mount, tar, and many others. If you want to access files larger
 538           than 2 Gigabytes, enable this option. Otherwise, leave it set to 'N'.
 539
 540 config BUSYBOX_CONFIG_CROSS_COMPILER_PREFIX
 541         string "Cross Compiler prefix"
 542         default ""
 543         help
 544           If you want to build BusyBox with a cross compiler, then you
 545           will need to set this to the cross-compiler prefix, for example,
 546           "i386-uclibc-".
 547
 548           Note that CROSS_COMPILE environment variable or
 549           "make CROSS_COMPILE=xxx ..." will override this selection.
 550
 551           Native builds leave this empty.
 552
 553 config BUSYBOX_CONFIG_EXTRA_CFLAGS
 554         string "Additional CFLAGS"
 555         default ""
 556         help
 557           Additional CFLAGS to pass to the compiler verbatim.
 558
 559 endmenu
 560
 561 menu 'Debugging Options'
 562
 563 config BUSYBOX_CONFIG_DEBUG
 564         bool "Build BusyBox with extra Debugging symbols"
 565         default n
 566         help
 567           Say Y here if you wish to examine BusyBox internals while applets are
 568           running. This increases the size of the binary considerably, and
 569           should only be used when doing development. If you are doing
 570           development and want to debug BusyBox, answer Y.
 571
 572           Most people should answer N.
 573
 574 config BUSYBOX_CONFIG_DEBUG_PESSIMIZE
 575         bool "Disable compiler optimizations"
 576         default n
 577         depends on BUSYBOX_CONFIG_DEBUG
 578         help
 579           The compiler's optimization of source code can eliminate and reorder
 580           code, resulting in an executable that's hard to understand when
 581           stepping through it with a debugger. This switches it off, resulting
 582           in a much bigger executable that more closely matches the source
 583           code.
 584
 585 config BUSYBOX_CONFIG_WERROR
 586         bool "Abort compilation on any warning"
 587         default n
 588         help
 589           Selecting this will add -Werror to gcc command line.
 590
 591           Most people should answer N.
 592
 593 choice
 594         prompt "Additional debugging library"
 595         default BUSYBOX_CONFIG_NO_DEBUG_LIB
 596         help
 597           Using an additional debugging library will make BusyBox become
 598           considerable larger and will cause it to run more slowly. You
 599           should always leave this option disabled for production use.
 600
 601           dmalloc support:
 602           ----------------
 603           This enables compiling with dmalloc ( http://dmalloc.com/ )
 604           which is an excellent public domain mem leak and malloc problem
 605           detector. To enable dmalloc, before running busybox you will
 606           want to properly set your environment, for example:
 607             export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
 608           The 'debug=' value is generated using the following command
 609             dmalloc -p log-stats -p log-non-free -p log-bad-space \
 610                -p log-elapsed-time -p check-fence -p check-heap \
 611                -p check-lists -p check-blank -p check-funcs -p realloc-copy \
 612                -p allow-free-null
 613
 614           Electric-fence support:
 615           -----------------------
 616           This enables compiling with Electric-fence support. Electric
 617           fence is another very useful malloc debugging library which uses
 618           your computer's virtual memory hardware to detect illegal memory
 619           accesses. This support will make BusyBox be considerable larger
 620           and run slower, so you should leave this option disabled unless
 621           you are hunting a hard to find memory problem.
 622
 623
 624 config BUSYBOX_CONFIG_NO_DEBUG_LIB
 625         bool "None"
 626
 627 config BUSYBOX_CONFIG_DMALLOC
 628         bool "Dmalloc"
 629
 630 config BUSYBOX_CONFIG_EFENCE
 631         bool "Electric-fence"
 632
 633 endchoice
 634
 635 ### config PARSE
 636 ###     bool "Uniform config file parser debugging applet: parse"
 637
 638 endmenu
 639
 640 menu 'Installation Options'
 641
 642 config BUSYBOX_CONFIG_INSTALL_NO_USR
 643         bool "Don't use /usr"
 644         default n
 645         help
 646           Disable use of /usr. Don't activate this option if you don't know
 647           that you really want this behaviour.
 648
 649 choice
 650         prompt "Applets links"
 651         default BUSYBOX_CONFIG_INSTALL_APPLET_SYMLINKS
 652         help
 653           Choose how you install applets links.
 654
 655 config BUSYBOX_CONFIG_INSTALL_APPLET_SYMLINKS
 656         bool "as soft-links"
 657         help
 658           Install applets as soft-links to the busybox binary. This needs some
 659           free inodes on the filesystem, but might help with filesystem
 660           generators that can't cope with hard-links.
 661
 662 config BUSYBOX_CONFIG_INSTALL_APPLET_HARDLINKS
 663         bool "as hard-links"
 664         help
 665           Install applets as hard-links to the busybox binary. This might
 666           count on a filesystem with few inodes.
 667
 668 config BUSYBOX_CONFIG_INSTALL_APPLET_SCRIPT_WRAPPERS
 669         bool "as script wrappers"
 670         help
 671           Install applets as script wrappers that call the busybox binary.
 672
 673 config BUSYBOX_CONFIG_INSTALL_APPLET_DONT
 674         bool "not installed"
 675         depends on BUSYBOX_CONFIG_FEATURE_INSTALLER || BUSYBOX_CONFIG_FEATURE_SH_STANDALONE || BUSYBOX_CONFIG_FEATURE_PREFER_APPLETS
 676         help
 677           Do not install applet links. Useful when using the -install feature
 678           or a standalone shell for rescue purposes.
 679
 680 endchoice
 681
 682 choice
 683         prompt "/bin/sh applet link"
 684         default BUSYBOX_CONFIG_INSTALL_SH_APPLET_SYMLINK
 685         depends on BUSYBOX_CONFIG_INSTALL_APPLET_SCRIPT_WRAPPERS
 686         help
 687           Choose how you install /bin/sh applet link.
 688
 689 config BUSYBOX_CONFIG_INSTALL_SH_APPLET_SYMLINK
 690         bool "as soft-link"
 691         help
 692           Install /bin/sh applet as soft-link to the busybox binary.
 693
 694 config BUSYBOX_CONFIG_INSTALL_SH_APPLET_HARDLINK
 695         bool "as hard-link"
 696         help
 697           Install /bin/sh applet as hard-link to the busybox binary.
 698
 699 config BUSYBOX_CONFIG_INSTALL_SH_APPLET_SCRIPT_WRAPPER
 700         bool "as script wrapper"
 701         help
 702           Install /bin/sh applet as script wrapper that call the busybox
 703           binary.
 704
 705 endchoice
 706
 707 config BUSYBOX_CONFIG_PREFIX
 708         string "BusyBox installation prefix"
 709         default "./_install"
 710         help
 711           Define your directory to install BusyBox files/subdirs in.
 712
 713 endmenu
 714
 715 source package/busybox/config/libbb/Config.in
 716
 717 endmenu
 718
 719 comment "Applets"
 720
 721 source package/busybox/config/archival/Config.in
 722 source package/busybox/config/coreutils/Config.in
 723 source package/busybox/config/console-tools/Config.in
 724 source package/busybox/config/debianutils/Config.in
 725 source package/busybox/config/editors/Config.in
 726 source package/busybox/config/findutils/Config.in
 727 source package/busybox/config/init/Config.in
 728 source package/busybox/config/loginutils/Config.in
 729 source package/busybox/config/e2fsprogs/Config.in
 730 source package/busybox/config/modutils/Config.in
 731 source package/busybox/config/util-linux/Config.in
 732 source package/busybox/config/miscutils/Config.in
 733 source package/busybox/config/networking/Config.in
 734 source package/busybox/config/printutils/Config.in
 735 source package/busybox/config/mailutils/Config.in
 736 source package/busybox/config/procps/Config.in
 737 source package/busybox/config/runit/Config.in
 738 source package/busybox/config/selinux/Config.in
 739 source package/busybox/config/shell/Config.in
 740 source package/busybox/config/sysklogd/Config.in