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_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 choice
  32         prompt "Buffer allocation policy"
  33         default BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_ON_STACK
  34         depends on BUSYBOX_CONFIG_NITPICK
  35         help
  36           There are 3 ways BusyBox can handle buffer allocations:
  37           - Use malloc. This costs code size for the call to xmalloc.
  38           - Put them on stack. For some very small machines with limited stack
  39             space, this can be deadly.  For most folks, this works just fine.
  40           - Put them in BSS. This works beautifully for computers with a real
  41             MMU (and OS support), but wastes runtime RAM for uCLinux. This
  42             behavior was the only one available for BusyBox versions 0.48 and
  43             earlier.
  44
  45 config BUSYBOX_CONFIG_FEATURE_BUFFERS_USE_MALLOC
  46         bool "Allocate with Malloc"
  47
  48 config BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_ON_STACK
  49         bool "Allocate on the Stack"
  50
  51 config BUSYBOX_CONFIG_FEATURE_BUFFERS_GO_IN_BSS
  52         bool "Allocate in the .bss section"
  53
  54 endchoice
  55
  56 config BUSYBOX_CONFIG_SHOW_USAGE
  57         bool "Show terse applet usage messages"
  58         default y
  59         help
  60           All BusyBox applets will show help messages when invoked with
  61           wrong arguments. You can turn off printing these terse usage
  62           messages if you say no here.
  63           This will save you up to 7k.
  64
  65 config BUSYBOX_CONFIG_FEATURE_VERBOSE_USAGE
  66         bool "Show verbose applet usage messages"
  67         default y
  68         select BUSYBOX_CONFIG_SHOW_USAGE
  69         help
  70           All BusyBox applets will show more verbose help messages when
  71           busybox is invoked with --help.  This will add a lot of text to the
  72           busybox binary.  In the default configuration, this will add about
  73           13k, but it can add much more depending on your configuration.
  74
  75 config BUSYBOX_CONFIG_FEATURE_COMPRESS_USAGE
  76         bool "Store applet usage messages in compressed form"
  77         default n
  78         depends on BUSYBOX_CONFIG_SHOW_USAGE && BUSYBOX_CONFIG_NITPICK
  79         help
  80           Store usage messages in compressed form, uncompress them on-the-fly
  81           when <applet> --help is called.
  82
  83           If you have a really tiny busybox with few applets enabled (and
  84           bunzip2 isn't one of them), the overhead of the decompressor might
  85           be noticeable.  Also, if you run executables directly from ROM
  86           and have very little memory, this might not be a win.  Otherwise,
  87           you probably want this.
  88
  89 config BUSYBOX_CONFIG_FEATURE_INSTALLER
  90         bool "Support --install [-s] to install applet links at runtime"
  91         default n
  92         help
  93           Enable 'busybox --install [-s]' support.  This will allow you to use
  94           busybox at runtime to create hard links or symlinks for all the
  95           applets that are compiled into busybox.  This feature requires the
  96           /proc filesystem.
  97
  98 config BUSYBOX_CONFIG_LOCALE_SUPPORT
  99         bool "Enable locale support (system needs locale for this to work)"
 100         default n
 101         help
 102           Enable this if your system has locale support and you would like
 103           busybox to support locale settings.
 104
 105 config BUSYBOX_CONFIG_GETOPT_LONG
 106         bool
 107         default y
 108 #       bool "Enable support for --long-options"
 109 #       default n
 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         depends on BUSYBOX_CONFIG_NITPICK
 128         help
 129           As a size optimization, busybox normally exits without explicitly
 130           freeing dynamically allocated memory or closing files.  This saves
 131           space since the OS will clean up for us, but it can confuse debuggers
 132           like valgrind, which report tons of memory and resource leaks.
 133
 134           Don't enable this unless you have a really good reason to clean
 135           things up manually.
 136
 137 config BUSYBOX_CONFIG_FEATURE_SUID
 138         bool "Support for SUID/SGID handling"
 139         default y
 140         help
 141           With this option you can install the busybox binary belonging
 142           to root with the suid bit set, and it'll and it'll automatically drop
 143           priviledges for applets that don't need root access.
 144
 145           If you're really paranoid and don't want to do this, build two
 146           busybox binaries with different applets in them (and the appropriate
 147           symlinks pointing to each binary), and only set the suid bit on the
 148           one that needs it.  The applets currently marked to need the suid bit
 149           are login, passwd, su, ping, traceroute, crontab, dnsd, ipcrm, ipcs,
 150           and vlock.
 151
 152 config BUSYBOX_CONFIG_FEATURE_SUID_CONFIG
 153         bool "Runtime SUID/SGID configuration via /etc/busybox.conf"
 154         default n if BUSYBOX_CONFIG_FEATURE_SUID
 155         depends on BUSYBOX_CONFIG_FEATURE_SUID
 156         help
 157           Allow the SUID / SGID state of an applet to be determined at runtime
 158           by checking /etc/busybox.conf.  (This is sort of a poor man's sudo.)
 159           The format of this file is as follows:
 160
 161           <applet> = [Ssx-][Ssx-][x-] (<username>|<uid>).(<groupname>|<gid>)
 162
 163           An example might help:
 164
 165           [SUID]
 166           su = ssx root.0 # applet su can be run by anyone and runs with euid=0/egid=0
 167           su = ssx        # exactly the same
 168
 169           mount = sx- root.disk # applet mount can be run by root and members of group disk
 170                                 # and runs with euid=0
 171
 172           cp = --- # disable applet cp for everyone
 173
 174           The file has to be owned by user root, group root and has to be
 175           writeable only by root:
 176                 (chown 0.0 /etc/busybox.conf; chmod 600 /etc/busybox.conf)
 177           The busybox executable has to be owned by user root, group
 178           root and has to be setuid root for this to work:
 179                 (chown 0.0 /bin/busybox; chmod 4755 /bin/busybox)
 180
 181           Robert 'sandman' Griebl has more information here:
 182           <url: http://www.softforge.de/bb/suid.html >.
 183
 184 config BUSYBOX_CONFIG_FEATURE_SUID_CONFIG_QUIET
 185         bool "Suppress warning message if /etc/busybox.conf is not readable"
 186         default n
 187         depends on BUSYBOX_CONFIG_FEATURE_SUID_CONFIG
 188         help
 189           /etc/busybox.conf should be readable by the user needing the SUID, check
 190           this option to avoid users to be notified about missing permissions.
 191
 192 config BUSYBOX_CONFIG_SELINUX
 193         bool "Support NSA Security Enhanced Linux"
 194         default n
 195         help
 196           Enable support for SELinux in applets ls, ps, and id.  Also provide
 197           the option of compiling in SELinux applets.
 198
 199           If you do not have a complete SELinux userland installed, this stuff
 200           will not compile. Go visit
 201                 http://www.nsa.gov/selinux/index.html
 202           to download the necessary stuff to allow busybox to compile with
 203           this option enabled. Specifially, libselinux 1.28 or better is
 204           directly required by busybox. If the installation is located in a
 205           non-standard directory, provide it by invoking make as follows:
 206                 CFLAGS=-I<libselinux-include-path> \
 207                 LDFLAGS=-L<libselinux-lib-path> \
 208                 make
 209
 210           Most people will leave this set to 'N'.
 211
 212 config BUSYBOX_CONFIG_BUSYBOX_EXEC_PATH
 213         string "Path to BusyBox executable"
 214         default "/proc/self/exe"
 215         help
 216           When Busybox applets need to run other busybox applets, BusyBox
 217           sometimes needs to exec() itself.  When the /proc filesystem is
 218           mounted, /proc/self/exe always points to the currently running
 219           executable.  If you haven't got /proc, set this to wherever you
 220           want to run BusyBox from.
 221
 222 endmenu
 223
 224 menu 'Build Options'
 225
 226 config BUSYBOX_CONFIG_STATIC
 227         bool "Build BusyBox as a static binary (no shared libs)"
 228         default n
 229         help
 230           If you want to build a static BusyBox binary, which does not
 231           use or require any shared libraries, then enable this option.
 232           This can cause BusyBox to be considerably larger, so you should
 233           leave this option false unless you have a good reason (i.e.
 234           your target platform does not support shared libraries, or
 235           you are building an initrd which doesn't need anything but
 236           BusyBox, etc).
 237
 238           Most people will leave this set to 'N'.
 239
 240 config BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 241         bool "Build shared libbusybox"
 242         default n
 243         help
 244           Build a shared library libbusybox.so which contains all
 245           libraries used inside busybox.
 246
 247           This is an experimental feature intended to support the upcoming
 248           "make standalone" mode.  Enabling it against the one big busybox
 249           binary serves no purpose (and increases the size).  You should
 250           almost certainly say "no" to this right now.
 251
 252 config BUSYBOX_CONFIG_FEATURE_FULL_LIBBUSYBOX
 253         bool "Feature-complete libbusybox"
 254         default n if !CONFIG_FEATURE_SHARED_BUSYBOX
 255         depends on BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 256         help
 257           Build a libbusybox with the complete feature-set, disregarding
 258           the actually selected config.
 259
 260           Normally, libbusybox will only contain the features which are
 261           used by busybox itself. If you plan to write a separate
 262           standalone application which uses libbusybox say 'Y'.
 263
 264           Note: libbusybox is GPL, not LGPL, and exports no stable API that
 265           might act as a copyright barrier.  We can and will modify the
 266           exported function set between releases (even minor version number
 267           changes), and happily break out-of-tree features.
 268
 269           Say 'N' if in doubt.
 270
 271 config BUSYBOX_CONFIG_FEATURE_SHARED_BUSYBOX
 272         bool "Use shared libbusybox for busybox"
 273         default n if BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 274         depends on !CONFIG_STATIC && BUSYBOX_CONFIG_BUILD_LIBBUSYBOX
 275         help
 276           Use libbusybox.so also for busybox itself.
 277           You need to have a working dynamic linker to use this variant.
 278
 279 config BUSYBOX_CONFIG_LFS
 280         bool
 281         default y
 282         select BUSYBOX_FDISK_SUPPORT_LARGE_DISKS
 283         help
 284           If you want to build BusyBox with large file support, then enable
 285           this option.  This will have no effect if your kernel or your C
 286           library lacks large file support for large files.  Some of the
 287           programs that can benefit from large file support include dd, gzip,
 288           cp, mount, tar, and many others.  If you want to access files larger
 289           than 2 Gigabytes, enable this option.  Otherwise, leave it set to 'N'.
 290
 291 config BUSYBOX_USING_CROSS_COMPILER
 292         bool
 293         default y
 294         help
 295           Do you want to build BusyBox with a Cross Compiler?  If so,
 296           then enable this option.  Otherwise leave it set to 'N'.
 297
 298 config BUSYBOX_CROSS_COMPILER_PREFIX
 299         string
 300         default "mipsel-uclibc-"
 301         depends on BUSYBOX_USING_CROSS_COMPILER
 302         help
 303           If you want to build BusyBox with a cross compiler, then you
 304           will need to set this to the cross-compiler prefix.  For example,
 305           if my cross-compiler is /usr/i386-linux-uclibc/bin/i386-uclibc-gcc
 306           then I would enter '/usr/i386-linux-uclibc/bin/i386-uclibc-' here,
 307           which will ensure the correct compiler is used.
 308
 309 config BUSYBOX_CONFIG_BUILD_AT_ONCE
 310         bool "Compile all sources at once"
 311         default n
 312         help
 313           Normally each source-file is compiled with one invocation of
 314           the compiler.
 315           If you set this option, all sources are compiled at once.
 316           This gives the compiler more opportunities to optimize which can
 317           result in smaller and/or faster binaries.
 318
 319           Setting this option will consume alot of memory, e.g. if you
 320           enable all applets with all features, gcc uses more than 300MB
 321           RAM during compilation of busybox.
 322
 323           This option is most likely only beneficial for newer compilers
 324           such as gcc-4.1 and above.
 325
 326           Say 'N' unless you know what you are doing.
 327
 328 endmenu
 329
 330 menu 'Debugging Options'
 331
 332 config BUSYBOX_CONFIG_DEBUG
 333         bool "Build BusyBox with extra Debugging symbols"
 334         default n
 335         help
 336           Say Y here if you wish to examine BusyBox internals while applets are
 337           running.  This increases the size of the binary considerably, and
 338           should only be used when doing development.  If you are doing
 339           development and want to debug BusyBox, answer Y.
 340
 341           Most people should answer N.
 342
 343 config BUSYBOX_CONFIG_DEBUG_PESSIMIZE
 344         bool "Disable compiler optimizations."
 345         default n
 346         depends on BUSYBOX_CONFIG_DEBUG
 347         help
 348           The compiler's optimization of source code can eliminate and reorder
 349           code, resulting in an executable that's hard to understand when
 350           stepping through it with a debugger.  This switches it off, resulting
 351           in a much bigger executable that more closely matches the source
 352           code.
 353
 354 choice
 355         prompt "Additional debugging library"
 356         default BUSYBOX_CONFIG_NO_DEBUG_LIB
 357         depends on BUSYBOX_CONFIG_DEBUG
 358         help
 359           Using an additional debugging library will make BusyBox become
 360           considerable larger and will cause it to run more slowly.  You
 361           should always leave this option disabled for production use.
 362
 363           dmalloc support:
 364           ----------------
 365           This enables compiling with dmalloc ( http://dmalloc.com/ )
 366           which is an excellent public domain mem leak and malloc problem
 367           detector.  To enable dmalloc, before running busybox you will
 368           want to properly set your environment, for example:
 369             export DMALLOC_OPTIONS=debug=0x34f47d83,inter=100,log=logfile
 370           The 'debug=' value is generated using the following command
 371             dmalloc -p log-stats -p log-non-free -p log-bad-space -p log-elapsed-time \
 372                -p check-fence -p check-heap -p check-lists -p check-blank \
 373                -p check-funcs -p realloc-copy -p allow-free-null
 374
 375           Electric-fence support:
 376           -----------------------
 377           This enables compiling with Electric-fence support.  Electric
 378           fence is another very useful malloc debugging library which uses
 379           your computer's virtual memory hardware to detect illegal memory
 380           accesses.  This support will make BusyBox be considerable larger
 381           and run slower, so you should leave this option disabled unless
 382           you are hunting a hard to find memory problem.
 383
 384
 385 config BUSYBOX_CONFIG_NO_DEBUG_LIB
 386         bool "None"
 387
 388 config BUSYBOX_CONFIG_DMALLOC
 389         bool "Dmalloc"
 390
 391 config BUSYBOX_CONFIG_EFENCE
 392         bool "Electric-fence"
 393
 394 endchoice
 395
 396 config BUSYBOX_CONFIG_DEBUG_YANK_SUSv2
 397         bool "Disable obsolete features removed before SUSv3?"
 398         default y
 399         help
 400           This option will disable backwards compatibility with SuSv2,
 401           specifically, old-style numeric options ('command -1 <file>')
 402           will not be supported in head, tail, and fold.  (Note: should
 403           yank from renice too.)
 404
 405 endmenu
 406
 407 menu 'Installation Options'
 408
 409 config BUSYBOX_CONFIG_INSTALL_NO_USR
 410         bool "Don't use /usr"
 411         default n
 412         help
 413           Disable use of /usr. Don't activate this option if you don't know
 414           that you really want this behaviour.
 415
 416 choice
 417        prompt "Applets links"
 418        default BUSYBOX_CONFIG_INSTALL_APPLET_SYMLINKS
 419        help
 420          Choose how you install applets links.
 421
 422 config BUSYBOX_CONFIG_INSTALL_APPLET_SYMLINKS
 423        bool "as soft-links"
 424        help
 425          Install applets as soft-links to the busybox binary. This needs some
 426          free inodes on the filesystem, but might help with filesystem
 427          generators that can't cope with hard-links.
 428
 429 config BUSYBOX_CONFIG_INSTALL_APPLET_HARDLINKS
 430        bool "as hard-links"
 431        help
 432          Install applets as hard-links to the busybox binary. This might count
 433          on a filesystem with few inodes.
 434
 435 config BUSYBOX_CONFIG_INSTALL_APPLET_DONT
 436        bool
 437        prompt "not installed"
 438        depends on BUSYBOX_CONFIG_FEATURE_INSTALLER || BUSYBOX_CONFIG_FEATURE_SH_STANDALONE_SHELL
 439        help
 440          Do not install applets links. Usefull when using the -install feature
 441          or a standalone shell for rescue pruposes.
 442
 443 endchoice
 444
 445 config BUSYBOX_PREFIX
 446         string
 447         default "./_install"
 448         help
 449           Define your directory to install BusyBox files/subdirs in.
 450
 451 endmenu
 452
 453 source package/busybox/config/libbb/Config.in
 454
 455 endmenu
 456
 457 comment "Applets"
 458
 459 source package/busybox/config/archival/Config.in
 460 source package/busybox/config/coreutils/Config.in
 461 source package/busybox/config/console-tools/Config.in
 462 source package/busybox/config/debianutils/Config.in
 463 source package/busybox/config/editors/Config.in
 464 source package/busybox/config/findutils/Config.in
 465 source package/busybox/config/init/Config.in
 466 source package/busybox/config/loginutils/Config.in
 467 source package/busybox/config/e2fsprogs/Config.in
 468 source package/busybox/config/modutils/Config.in
 469 source package/busybox/config/util-linux/Config.in
 470 source package/busybox/config/miscutils/Config.in
 471 source package/busybox/config/networking/Config.in
 472 source package/busybox/config/procps/Config.in
 473 source package/busybox/config/shell/Config.in
 474 source package/busybox/config/sysklogd/Config.in