| 1 | # DO NOT EDIT. This file is generated from Config.src |
| 2 | # |
| 3 | # For a description of the syntax of this configuration file, |
| 4 | # see scripts/kbuild/config-language.txt. |
| 5 | # |
| 6 | |
| 7 | menu "Init Utilities" |
| 8 | |
| 9 | config BUSYBOX_CONFIG_BOOTCHARTD |
| 10 | bool "bootchartd" |
| 11 | default n |
| 12 | help |
| 13 | bootchartd is commonly used to profile the boot process |
| 14 | for the purpose of speeding it up. In this case, it is started |
| 15 | by the kernel as the init process. This is configured by adding |
| 16 | the init=/sbin/bootchartd option to the kernel command line. |
| 17 | |
| 18 | It can also be used to monitor the resource usage of a specific |
| 19 | application or the running system in general. In this case, |
| 20 | bootchartd is started interactively by running bootchartd start |
| 21 | and stopped using bootchartd stop. |
| 22 | |
| 23 | config BUSYBOX_CONFIG_FEATURE_BOOTCHARTD_BLOATED_HEADER |
| 24 | bool "Compatible, bloated header" |
| 25 | default n |
| 26 | depends on BUSYBOX_CONFIG_BOOTCHARTD |
| 27 | help |
| 28 | Create extended header file compatible with "big" bootchartd. |
| 29 | "Big" bootchartd is a shell script and it dumps some |
| 30 | "convenient" info int the header, such as: |
| 31 | title = Boot chart for `hostname` (`date`) |
| 32 | system.uname = `uname -srvm` |
| 33 | system.release = `cat /etc/DISTRO-release` |
| 34 | system.cpu = `grep '^model name' /proc/cpuinfo | head -1` ($cpucount) |
| 35 | system.kernel.options = `cat /proc/cmdline` |
| 36 | This data is not mandatory for bootchart graph generation, |
| 37 | and is considered bloat. Nevertheless, this option |
| 38 | makes bootchartd applet to dump a subset of it. |
| 39 | |
| 40 | config BUSYBOX_CONFIG_FEATURE_BOOTCHARTD_CONFIG_FILE |
| 41 | bool "Support bootchartd.conf" |
| 42 | default n |
| 43 | depends on BUSYBOX_CONFIG_BOOTCHARTD |
| 44 | help |
| 45 | Enable reading and parsing of $PWD/bootchartd.conf |
| 46 | and /etc/bootchartd.conf files. |
| 47 | config BUSYBOX_CONFIG_HALT |
| 48 | bool "poweroff, halt, and reboot" |
| 49 | default y |
| 50 | help |
| 51 | Stop all processes and either halt, reboot, or power off the system. |
| 52 | |
| 53 | config BUSYBOX_CONFIG_FEATURE_CALL_TELINIT |
| 54 | bool "Call telinit on shutdown and reboot" |
| 55 | default n |
| 56 | depends on BUSYBOX_CONFIG_HALT && !BUSYBOX_CONFIG_INIT |
| 57 | help |
| 58 | Call an external program (normally telinit) to facilitate |
| 59 | a switch to a proper runlevel. |
| 60 | |
| 61 | This option is only available if you selected halt and friends, |
| 62 | but did not select init. |
| 63 | |
| 64 | config BUSYBOX_CONFIG_TELINIT_PATH |
| 65 | string "Path to telinit executable" |
| 66 | default "/sbin/telinit" |
| 67 | depends on BUSYBOX_CONFIG_FEATURE_CALL_TELINIT |
| 68 | help |
| 69 | When busybox halt and friends have to call external telinit |
| 70 | to facilitate proper shutdown, this path is to be used when |
| 71 | locating telinit executable. |
| 72 | config BUSYBOX_CONFIG_INIT |
| 73 | bool "init" |
| 74 | default y |
| 75 | select BUSYBOX_CONFIG_FEATURE_SYSLOG |
| 76 | help |
| 77 | init is the first program run when the system boots. |
| 78 | |
| 79 | config BUSYBOX_CONFIG_FEATURE_USE_INITTAB |
| 80 | bool "Support reading an inittab file" |
| 81 | default y |
| 82 | depends on BUSYBOX_CONFIG_INIT |
| 83 | help |
| 84 | Allow init to read an inittab file when the system boot. |
| 85 | |
| 86 | config BUSYBOX_CONFIG_FEATURE_KILL_REMOVED |
| 87 | bool "Support killing processes that have been removed from inittab" |
| 88 | default n |
| 89 | depends on BUSYBOX_CONFIG_FEATURE_USE_INITTAB |
| 90 | help |
| 91 | When respawn entries are removed from inittab and a SIGHUP is |
| 92 | sent to init, this option will make init kill the processes |
| 93 | that have been removed. |
| 94 | |
| 95 | config BUSYBOX_CONFIG_FEATURE_KILL_DELAY |
| 96 | int "How long to wait between TERM and KILL (0 - send TERM only)" if FEATURE_KILL_REMOVED |
| 97 | range 0 1024 |
| 98 | default 0 |
| 99 | depends on BUSYBOX_CONFIG_FEATURE_KILL_REMOVED |
| 100 | help |
| 101 | With nonzero setting, init sends TERM, forks, child waits N |
| 102 | seconds, sends KILL and exits. Setting it too high is unwise |
| 103 | (child will hang around for too long and could actually kill |
| 104 | the wrong process!) |
| 105 | |
| 106 | config BUSYBOX_CONFIG_FEATURE_INIT_SCTTY |
| 107 | bool "Run commands with leading dash with controlling tty" |
| 108 | default n |
| 109 | depends on BUSYBOX_CONFIG_INIT |
| 110 | help |
| 111 | If this option is enabled, init will try to give a controlling |
| 112 | tty to any command which has leading hyphen (often it's "-/bin/sh"). |
| 113 | More precisely, init will do "ioctl(STDIN_FILENO, TIOCSCTTY, 0)". |
| 114 | If device attached to STDIN_FILENO can be a ctty but is not yet |
| 115 | a ctty for other session, it will become this process' ctty. |
| 116 | This is not the traditional init behavour, but is often what you want |
| 117 | in an embedded system where the console is only accessed during |
| 118 | development or for maintenance. |
| 119 | NB: using cttyhack applet may work better. |
| 120 | |
| 121 | config BUSYBOX_CONFIG_FEATURE_INIT_SYSLOG |
| 122 | bool "Enable init to write to syslog" |
| 123 | default y |
| 124 | depends on BUSYBOX_CONFIG_INIT |
| 125 | |
| 126 | config BUSYBOX_CONFIG_FEATURE_EXTRA_QUIET |
| 127 | bool "Be _extra_ quiet on boot" |
| 128 | default n |
| 129 | depends on BUSYBOX_CONFIG_INIT |
| 130 | help |
| 131 | Prevent init from logging some messages to the console during boot. |
| 132 | |
| 133 | config BUSYBOX_CONFIG_FEATURE_INIT_COREDUMPS |
| 134 | bool "Support dumping core for child processes (debugging only)" |
| 135 | default n |
| 136 | depends on BUSYBOX_CONFIG_INIT |
| 137 | help |
| 138 | If this option is enabled and the file /.init_enable_core |
| 139 | exists, then init will call setrlimit() to allow unlimited |
| 140 | core file sizes. If this option is disabled, processes |
| 141 | will not generate any core files. |
| 142 | |
| 143 | config BUSYBOX_CONFIG_FEATURE_INITRD |
| 144 | bool "Support running init from within an initrd (not initramfs)" |
| 145 | default n |
| 146 | depends on BUSYBOX_CONFIG_INIT |
| 147 | help |
| 148 | Legacy support for running init under the old-style initrd. Allows |
| 149 | the name linuxrc to act as init, and it doesn't assume init is PID 1. |
| 150 | |
| 151 | This does not apply to initramfs, which runs /init as PID 1 and |
| 152 | requires no special support. |
| 153 | |
| 154 | config BUSYBOX_CONFIG_INIT_TERMINAL_TYPE |
| 155 | string "Initial terminal type" |
| 156 | default "linux" |
| 157 | depends on BUSYBOX_CONFIG_INIT |
| 158 | help |
| 159 | This is the initial value set by init for the TERM environment |
| 160 | variable. This variable is used by programs which make use of |
| 161 | extended terminal capabilities. |
| 162 | |
| 163 | Note that on Linux, init attempts to detect serial terminal and |
| 164 | sets TERM to "vt102" if one is found. |
| 165 | config BUSYBOX_CONFIG_MESG |
| 166 | bool "mesg" |
| 167 | default n |
| 168 | help |
| 169 | Mesg controls access to your terminal by others. It is typically |
| 170 | used to allow or disallow other users to write to your terminal |
| 171 | |
| 172 | config BUSYBOX_CONFIG_FEATURE_MESG_ENABLE_ONLY_GROUP |
| 173 | bool "Enable writing to tty only by group, not by everybody" |
| 174 | default n |
| 175 | depends on BUSYBOX_CONFIG_MESG |
| 176 | help |
| 177 | Usually, ttys are owned by group "tty", and "write" tool is |
| 178 | setgid to this group. This way, "mesg y" only needs to enable |
| 179 | "write by owning group" bit in tty mode. |
| 180 | |
| 181 | If you set this option to N, "mesg y" will enable writing |
| 182 | by anybody at all. This is not recommended. |
| 183 | |
| 184 | endmenu |
| 185 | |
