diff options
| author | Denys Vlasenko <vda.linux@googlemail.com> | 2010-06-04 20:10:51 +0200 |
|---|---|---|
| committer | Denys Vlasenko <vda.linux@googlemail.com> | 2010-06-04 20:10:51 +0200 |
| commit | da929a95aace0e79fbc621af2ab03c76d74d5fcb (patch) | |
| tree | 2b7dd63658eef78fde7604772d9815283c2c1cdf /init/Config.src | |
| parent | e4070cb0d7586037c6fcf0f0f00d8d5b97f649d3 (diff) | |
| download | busybox-w32-da929a95aace0e79fbc621af2ab03c76d74d5fcb.tar.gz busybox-w32-da929a95aace0e79fbc621af2ab03c76d74d5fcb.tar.bz2 busybox-w32-da929a95aace0e79fbc621af2ab03c76d74d5fcb.zip | |
mass renaming Kbuild -> Kbuild.src, Config.in -> Config.src
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Diffstat (limited to 'init/Config.src')
| -rw-r--r-- | init/Config.src | 137 |
1 files changed, 137 insertions, 0 deletions
diff --git a/init/Config.src b/init/Config.src new file mode 100644 index 000000000..76d509207 --- /dev/null +++ b/init/Config.src | |||
| @@ -0,0 +1,137 @@ | |||
| 1 | # | ||
| 2 | # For a description of the syntax of this configuration file, | ||
| 3 | # see scripts/kbuild/config-language.txt. | ||
| 4 | # | ||
| 5 | |||
| 6 | menu "Init Utilities" | ||
| 7 | |||
| 8 | config INIT | ||
| 9 | bool "init" | ||
| 10 | default n | ||
| 11 | select FEATURE_SYSLOG | ||
| 12 | help | ||
| 13 | init is the first program run when the system boots. | ||
| 14 | |||
| 15 | config FEATURE_USE_INITTAB | ||
| 16 | bool "Support reading an inittab file" | ||
| 17 | default y | ||
| 18 | depends on INIT | ||
| 19 | help | ||
| 20 | Allow init to read an inittab file when the system boot. | ||
| 21 | |||
| 22 | config FEATURE_KILL_REMOVED | ||
| 23 | bool "Support killing processes that have been removed from inittab" | ||
| 24 | default y | ||
| 25 | depends on FEATURE_USE_INITTAB | ||
| 26 | help | ||
| 27 | When respawn entries are removed from inittab and a SIGHUP is | ||
| 28 | sent to init, this feature will kill the processes that have | ||
| 29 | been removed. | ||
| 30 | |||
| 31 | config FEATURE_KILL_DELAY | ||
| 32 | int "How long to wait between TERM and KILL (0 - send TERM only)" if FEATURE_KILL_REMOVED | ||
| 33 | range 0 1024 | ||
| 34 | default 0 | ||
| 35 | depends on FEATURE_KILL_REMOVED | ||
| 36 | help | ||
| 37 | With nonzero setting, init sends TERM, forks, child waits N | ||
| 38 | seconds, sends KILL and exits. Setting it too high is unwise | ||
| 39 | (child will hang around for too long and could actually kill | ||
| 40 | the wrong process!) | ||
| 41 | |||
| 42 | config FEATURE_INIT_SCTTY | ||
| 43 | bool "Run commands with leading dash with controlling tty" | ||
| 44 | default n | ||
| 45 | depends on INIT | ||
| 46 | help | ||
| 47 | If this option is enabled, init will try to give a controlling | ||
| 48 | tty to any command which has leading hyphen (often it's "-/bin/sh"). | ||
| 49 | More precisely, init will do "ioctl(STDIN_FILENO, TIOCSCTTY, 0)". | ||
| 50 | If device attached to STDIN_FILENO can be a ctty but is not yet | ||
| 51 | a ctty for other session, it will become this process' ctty. | ||
| 52 | This is not the traditional init behavour, but is often what you want | ||
| 53 | in an embedded system where the console is only accessed during | ||
| 54 | development or for maintenance. | ||
| 55 | NB: using cttyhack applet may work better. | ||
| 56 | |||
| 57 | config FEATURE_INIT_SYSLOG | ||
| 58 | bool "Enable init to write to syslog" | ||
| 59 | default n | ||
| 60 | depends on INIT | ||
| 61 | |||
| 62 | config FEATURE_EXTRA_QUIET | ||
| 63 | bool "Be _extra_ quiet on boot" | ||
| 64 | default y | ||
| 65 | depends on INIT | ||
| 66 | help | ||
| 67 | Prevent init from logging some messages to the console during boot. | ||
| 68 | |||
| 69 | config FEATURE_INIT_COREDUMPS | ||
| 70 | bool "Support dumping core for child processes (debugging only)" | ||
| 71 | default n | ||
| 72 | depends on INIT | ||
| 73 | help | ||
| 74 | If this option is enabled and the file /.init_enable_core | ||
| 75 | exists, then init will call setrlimit() to allow unlimited | ||
| 76 | core file sizes. If this option is disabled, processes | ||
| 77 | will not generate any core files. | ||
| 78 | |||
| 79 | config FEATURE_INITRD | ||
| 80 | bool "Support running init from within an initrd (not initramfs)" | ||
| 81 | default y | ||
| 82 | depends on INIT | ||
| 83 | help | ||
| 84 | Legacy support for running init under the old-style initrd. Allows | ||
| 85 | the name linuxrc to act as init, and it doesn't assume init is PID 1. | ||
| 86 | |||
| 87 | This does not apply to initramfs, which runs /init as PID 1 and | ||
| 88 | requires no special support. | ||
| 89 | |||
| 90 | config HALT | ||
| 91 | bool "poweroff, halt, and reboot" | ||
| 92 | default n | ||
| 93 | help | ||
| 94 | Stop all processes and either halt, reboot, or power off the system. | ||
| 95 | |||
| 96 | config FEATURE_CALL_TELINIT | ||
| 97 | bool "Call telinit on shutdown and reboot" | ||
| 98 | default n | ||
| 99 | depends on HALT && !INIT | ||
| 100 | help | ||
| 101 | Call an external program (normally telinit) to facilitate | ||
| 102 | a switch to a proper runlevel. | ||
| 103 | |||
| 104 | This option is only available if you selected halt and friends, | ||
| 105 | but did not select init. | ||
| 106 | |||
| 107 | config TELINIT_PATH | ||
| 108 | string "Path to telinit executable" | ||
| 109 | default "/sbin/telinit" | ||
| 110 | depends on FEATURE_CALL_TELINIT | ||
| 111 | help | ||
| 112 | When busybox halt and friends have to call external telinit | ||
| 113 | to facilitate proper shutdown, this path is to be used when | ||
| 114 | locating telinit executable. | ||
| 115 | |||
| 116 | config MESG | ||
| 117 | bool "mesg" | ||
| 118 | default n | ||
| 119 | help | ||
| 120 | Mesg controls access to your terminal by others. It is typically | ||
| 121 | used to allow or disallow other users to write to your terminal | ||
| 122 | |||
| 123 | config BOOTCHARTD | ||
| 124 | bool "bootchartd" | ||
| 125 | default n | ||
| 126 | help | ||
| 127 | bootchartd is commonly used to profile the boot process | ||
| 128 | for the purpose of speeding it up. In this case, it is started | ||
| 129 | by the kernel as the init process. This is configured by adding | ||
| 130 | the init=/sbin/bootchartd option to the kernel command line. | ||
| 131 | |||
| 132 | It can also be used to monitor the resource usage of a specific | ||
| 133 | application or the running system in general. In this case, | ||
| 134 | bootchartd is started interactively by running bootchartd start | ||
| 135 | and stopped using bootchartd stop. | ||
| 136 | |||
| 137 | endmenu | ||
