OpenWrt – Blame information for rev 3
?pathlinks?
Rev | Author | Line No. | Line |
---|---|---|---|
1 | office | 1 | # DO NOT EDIT. This file is generated from Config.src |
2 | # |
||
3 | # For a description of the syntax of this configuration file, |
||
3 | office | 4 | # see scripts/kbuild/config-language.txt. |
1 | office | 5 | # |
6 | |||
7 | menu "Init Utilities" |
||
8 | |||
9 | config BUSYBOX_CONFIG_BOOTCHARTD |
||
3 | office | 10 | bool "bootchartd" |
1 | office | 11 | default BUSYBOX_DEFAULT_BOOTCHARTD |
12 | help |
||
3 | office | 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. |
||
1 | office | 17 | |
3 | office | 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. |
||
1 | office | 22 | |
23 | config BUSYBOX_CONFIG_FEATURE_BOOTCHARTD_BLOATED_HEADER |
||
24 | bool "Compatible, bloated header" |
||
25 | default BUSYBOX_DEFAULT_FEATURE_BOOTCHARTD_BLOATED_HEADER |
||
26 | depends on BUSYBOX_CONFIG_BOOTCHARTD |
||
27 | help |
||
3 | office | 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. |
||
1 | office | 39 | |
40 | config BUSYBOX_CONFIG_FEATURE_BOOTCHARTD_CONFIG_FILE |
||
41 | bool "Support bootchartd.conf" |
||
42 | default BUSYBOX_DEFAULT_FEATURE_BOOTCHARTD_CONFIG_FILE |
||
43 | depends on BUSYBOX_CONFIG_BOOTCHARTD |
||
44 | help |
||
3 | office | 45 | Enable reading and parsing of $PWD/bootchartd.conf |
46 | and /etc/bootchartd.conf files. |
||
1 | office | 47 | config BUSYBOX_CONFIG_HALT |
3 | office | 48 | bool "halt" |
1 | office | 49 | default BUSYBOX_DEFAULT_HALT |
50 | help |
||
3 | office | 51 | Stop all processes and halt the system. |
1 | office | 52 | |
53 | config BUSYBOX_CONFIG_POWEROFF |
||
3 | office | 54 | bool "poweroff" |
1 | office | 55 | default BUSYBOX_DEFAULT_POWEROFF |
56 | help |
||
3 | office | 57 | Stop all processes and power off the system. |
1 | office | 58 | |
59 | config BUSYBOX_CONFIG_REBOOT |
||
3 | office | 60 | bool "reboot" |
1 | office | 61 | default BUSYBOX_DEFAULT_REBOOT |
62 | help |
||
3 | office | 63 | Stop all processes and reboot the system. |
1 | office | 64 | |
65 | config BUSYBOX_CONFIG_FEATURE_CALL_TELINIT |
||
66 | bool "Call telinit on shutdown and reboot" |
||
67 | default BUSYBOX_DEFAULT_FEATURE_CALL_TELINIT |
||
68 | depends on (BUSYBOX_CONFIG_HALT || BUSYBOX_CONFIG_POWEROFF || BUSYBOX_CONFIG_REBOOT) && !BUSYBOX_CONFIG_INIT |
||
69 | help |
||
3 | office | 70 | Call an external program (normally telinit) to facilitate |
71 | a switch to a proper runlevel. |
||
1 | office | 72 | |
3 | office | 73 | This option is only available if you selected halt and friends, |
74 | but did not select init. |
||
1 | office | 75 | |
76 | config BUSYBOX_CONFIG_TELINIT_PATH |
||
77 | string "Path to telinit executable" |
||
78 | default BUSYBOX_DEFAULT_TELINIT_PATH |
||
79 | depends on BUSYBOX_CONFIG_FEATURE_CALL_TELINIT |
||
80 | help |
||
3 | office | 81 | When busybox halt and friends have to call external telinit |
82 | to facilitate proper shutdown, this path is to be used when |
||
83 | locating telinit executable. |
||
1 | office | 84 | config BUSYBOX_CONFIG_INIT |
3 | office | 85 | bool "init" |
1 | office | 86 | default BUSYBOX_DEFAULT_INIT |
87 | select BUSYBOX_CONFIG_FEATURE_SYSLOG |
||
88 | help |
||
3 | office | 89 | init is the first program run when the system boots. |
1 | office | 90 | |
91 | config BUSYBOX_CONFIG_LINUXRC |
||
92 | bool "linuxrc: support running init from initrd (not initramfs)" |
||
93 | default BUSYBOX_DEFAULT_LINUXRC |
||
94 | select BUSYBOX_CONFIG_FEATURE_SYSLOG |
||
95 | help |
||
3 | office | 96 | Legacy support for running init under the old-style initrd. Allows |
97 | the name linuxrc to act as init, and it doesn't assume init is PID 1. |
||
1 | office | 98 | |
3 | office | 99 | This does not apply to initramfs, which runs /init as PID 1 and |
100 | requires no special support. |
||
1 | office | 101 | |
102 | config BUSYBOX_CONFIG_FEATURE_USE_INITTAB |
||
103 | bool "Support reading an inittab file" |
||
104 | default BUSYBOX_DEFAULT_FEATURE_USE_INITTAB |
||
105 | depends on BUSYBOX_CONFIG_INIT || BUSYBOX_CONFIG_LINUXRC |
||
106 | help |
||
3 | office | 107 | Allow init to read an inittab file when the system boot. |
1 | office | 108 | |
109 | config BUSYBOX_CONFIG_FEATURE_KILL_REMOVED |
||
110 | bool "Support killing processes that have been removed from inittab" |
||
111 | default BUSYBOX_DEFAULT_FEATURE_KILL_REMOVED |
||
112 | depends on BUSYBOX_CONFIG_FEATURE_USE_INITTAB |
||
113 | help |
||
3 | office | 114 | When respawn entries are removed from inittab and a SIGHUP is |
115 | sent to init, this option will make init kill the processes |
||
116 | that have been removed. |
||
1 | office | 117 | |
118 | config BUSYBOX_CONFIG_FEATURE_KILL_DELAY |
||
119 | int "How long to wait between TERM and KILL (0 - send TERM only)" if FEATURE_KILL_REMOVED |
||
120 | range 0 1024 |
||
121 | default BUSYBOX_DEFAULT_FEATURE_KILL_DELAY |
||
122 | depends on BUSYBOX_CONFIG_FEATURE_KILL_REMOVED |
||
123 | help |
||
3 | office | 124 | With nonzero setting, init sends TERM, forks, child waits N |
125 | seconds, sends KILL and exits. Setting it too high is unwise |
||
126 | (child will hang around for too long and could actually kill |
||
127 | the wrong process!) |
||
1 | office | 128 | |
129 | config BUSYBOX_CONFIG_FEATURE_INIT_SCTTY |
||
130 | bool "Run commands with leading dash with controlling tty" |
||
131 | default BUSYBOX_DEFAULT_FEATURE_INIT_SCTTY |
||
132 | depends on BUSYBOX_CONFIG_INIT || BUSYBOX_CONFIG_LINUXRC |
||
133 | help |
||
3 | office | 134 | If this option is enabled, init will try to give a controlling |
135 | tty to any command which has leading hyphen (often it's "-/bin/sh"). |
||
136 | More precisely, init will do "ioctl(STDIN_FILENO, TIOCSCTTY, 0)". |
||
137 | If device attached to STDIN_FILENO can be a ctty but is not yet |
||
138 | a ctty for other session, it will become this process' ctty. |
||
139 | This is not the traditional init behavour, but is often what you want |
||
140 | in an embedded system where the console is only accessed during |
||
141 | development or for maintenance. |
||
142 | NB: using cttyhack applet may work better. |
||
1 | office | 143 | |
144 | config BUSYBOX_CONFIG_FEATURE_INIT_SYSLOG |
||
145 | bool "Enable init to write to syslog" |
||
146 | default BUSYBOX_DEFAULT_FEATURE_INIT_SYSLOG |
||
147 | depends on BUSYBOX_CONFIG_INIT || BUSYBOX_CONFIG_LINUXRC |
||
148 | help |
||
3 | office | 149 | If selected, some init messages are sent to syslog. |
150 | Otherwise, they are sent to VT #5 if linux virtual tty is detected |
||
151 | (if not, no separate logging is done). |
||
1 | office | 152 | |
153 | config BUSYBOX_CONFIG_FEATURE_INIT_QUIET |
||
154 | bool "Be quiet on boot (no 'init started:' message)" |
||
155 | default BUSYBOX_DEFAULT_FEATURE_INIT_QUIET |
||
156 | depends on BUSYBOX_CONFIG_INIT || BUSYBOX_CONFIG_LINUXRC |
||
157 | |||
158 | config BUSYBOX_CONFIG_FEATURE_INIT_COREDUMPS |
||
159 | bool "Support dumping core for child processes (debugging only)" |
||
160 | default BUSYBOX_DEFAULT_FEATURE_INIT_COREDUMPS # not Y because this is a debug option |
||
161 | depends on BUSYBOX_CONFIG_INIT || BUSYBOX_CONFIG_LINUXRC |
||
162 | help |
||
3 | office | 163 | If this option is enabled and the file /.init_enable_core |
164 | exists, then init will call setrlimit() to allow unlimited |
||
165 | core file sizes. If this option is disabled, processes |
||
166 | will not generate any core files. |
||
1 | office | 167 | |
168 | config BUSYBOX_CONFIG_INIT_TERMINAL_TYPE |
||
169 | string "Initial terminal type" |
||
170 | default BUSYBOX_DEFAULT_INIT_TERMINAL_TYPE |
||
171 | depends on BUSYBOX_CONFIG_INIT || BUSYBOX_CONFIG_LINUXRC |
||
172 | help |
||
3 | office | 173 | This is the initial value set by init for the TERM environment |
174 | variable. This variable is used by programs which make use of |
||
175 | extended terminal capabilities. |
||
1 | office | 176 | |
3 | office | 177 | Note that on Linux, init attempts to detect serial terminal and |
178 | sets TERM to "vt102" if one is found. |
||
1 | office | 179 | |
180 | config BUSYBOX_CONFIG_FEATURE_INIT_MODIFY_CMDLINE |
||
181 | bool "Clear init's command line" |
||
182 | default BUSYBOX_DEFAULT_FEATURE_INIT_MODIFY_CMDLINE |
||
183 | depends on BUSYBOX_CONFIG_INIT || BUSYBOX_CONFIG_LINUXRC |
||
184 | help |
||
3 | office | 185 | When launched as PID 1 and after parsing its arguments, init |
186 | wipes all the arguments but argv[0] and rewrites argv[0] to |
||
187 | contain only "init", so that its command line appears solely as |
||
188 | "init" in tools such as ps. |
||
189 | If this option is set to Y, init will keep its original behavior, |
||
190 | otherwise, all the arguments including argv[0] will be preserved, |
||
191 | be they parsed or ignored by init. |
||
192 | The original command-line used to launch init can then be |
||
193 | retrieved in /proc/1/cmdline on Linux, for example. |
||
1 | office | 194 | |
195 | endmenu |