2 # For a description of the syntax of this configuration file,
3 # see scripts/kbuild/config-language.txt.
8 config BUSYBOX_CONFIG_INIT
11 select BUSYBOX_CONFIG_FEATURE_SYSLOG
13 init is the first program run when the system boots.
15 config BUSYBOX_CONFIG_FEATURE_USE_INITTAB
16 bool "Support reading an inittab file"
18 depends on BUSYBOX_CONFIG_INIT
20 Allow init to read an inittab file when the system boot.
22 config BUSYBOX_CONFIG_FEATURE_KILL_REMOVED
23 bool "Support killing processes that have been removed from inittab"
25 depends on BUSYBOX_CONFIG_FEATURE_USE_INITTAB
27 When respawn entries are removed from inittab and a SIGHUP is
28 sent to init, this feature will kill the processes that have
31 config BUSYBOX_CONFIG_FEATURE_KILL_DELAY
32 int "How long to wait between TERM and KILL (0 - send TERM only)" if FEATURE_KILL_REMOVED
35 depends on BUSYBOX_CONFIG_FEATURE_KILL_REMOVED
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
42 config BUSYBOX_CONFIG_FEATURE_INIT_SCTTY
43 bool "Run commands with leading dash with controlling tty"
45 depends on BUSYBOX_CONFIG_INIT
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.
57 config BUSYBOX_CONFIG_FEATURE_INIT_SYSLOG
58 bool "Enable init to write to syslog"
60 depends on BUSYBOX_CONFIG_INIT
62 config BUSYBOX_CONFIG_FEATURE_EXTRA_QUIET
63 bool "Be _extra_ quiet on boot"
65 depends on BUSYBOX_CONFIG_INIT
67 Prevent init from logging some messages to the console during boot.
69 config BUSYBOX_CONFIG_FEATURE_INIT_COREDUMPS
70 bool "Support dumping core for child processes (debugging only)"
72 depends on BUSYBOX_CONFIG_INIT
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.
79 config BUSYBOX_CONFIG_FEATURE_INITRD
80 bool "Support running init from within an initrd (not initramfs)"
82 depends on BUSYBOX_CONFIG_INIT
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.
87 This does not apply to initramfs, which runs /init as PID 1 and
88 requires no special support.
90 config BUSYBOX_CONFIG_HALT
91 bool "poweroff, halt, and reboot"
94 Stop all processes and either halt, reboot, or power off the system.
96 config BUSYBOX_CONFIG_FEATURE_CALL_TELINIT
97 bool "Call telinit on shutdown and reboot"
99 depends on BUSYBOX_CONFIG_HALT && !BUSYBOX_CONFIG_INIT
101 Call an external program (normally telinit) to facilitate
102 a switch to a proper runlevel.
104 This option is only available if you selected halt and friends,
105 but did not select init.
107 config BUSYBOX_CONFIG_TELINIT_PATH
108 string "Path to telinit executable"
109 default "/sbin/telinit"
110 depends on BUSYBOX_CONFIG_FEATURE_CALL_TELINIT
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.
116 config BUSYBOX_CONFIG_MESG
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