config BUSYBOX_CONFIG_BOOTCHARTD
bool "bootchartd"
- default n
+ default BUSYBOX_DEFAULT_BOOTCHARTD
help
bootchartd is commonly used to profile the boot process
for the purpose of speeding it up. In this case, it is started
config BUSYBOX_CONFIG_FEATURE_BOOTCHARTD_BLOATED_HEADER
bool "Compatible, bloated header"
- default n
+ default BUSYBOX_DEFAULT_FEATURE_BOOTCHARTD_BLOATED_HEADER
depends on BUSYBOX_CONFIG_BOOTCHARTD
help
Create extended header file compatible with "big" bootchartd.
config BUSYBOX_CONFIG_FEATURE_BOOTCHARTD_CONFIG_FILE
bool "Support bootchartd.conf"
- default n
+ default BUSYBOX_DEFAULT_FEATURE_BOOTCHARTD_CONFIG_FILE
depends on BUSYBOX_CONFIG_BOOTCHARTD
help
Enable reading and parsing of $PWD/bootchartd.conf
and /etc/bootchartd.conf files.
config BUSYBOX_CONFIG_HALT
bool "poweroff, halt, and reboot"
- default y
+ default BUSYBOX_DEFAULT_HALT
help
Stop all processes and either halt, reboot, or power off the system.
config BUSYBOX_CONFIG_FEATURE_CALL_TELINIT
bool "Call telinit on shutdown and reboot"
- default n
+ default BUSYBOX_DEFAULT_FEATURE_CALL_TELINIT
depends on BUSYBOX_CONFIG_HALT && !BUSYBOX_CONFIG_INIT
help
Call an external program (normally telinit) to facilitate
config BUSYBOX_CONFIG_TELINIT_PATH
string "Path to telinit executable"
- default "/sbin/telinit"
+ default BUSYBOX_DEFAULT_TELINIT_PATH
depends on BUSYBOX_CONFIG_FEATURE_CALL_TELINIT
help
When busybox halt and friends have to call external telinit
locating telinit executable.
config BUSYBOX_CONFIG_INIT
bool "init"
- default n
+ default BUSYBOX_DEFAULT_INIT
select BUSYBOX_CONFIG_FEATURE_SYSLOG
- depends on BROKEN
help
init is the first program run when the system boots.
+config BUSYBOX_CONFIG_LINUXRC
+ bool "Support running init from within an initrd (not initramfs)"
+ default BUSYBOX_DEFAULT_LINUXRC
+ select BUSYBOX_CONFIG_FEATURE_SYSLOG
+ help
+ Legacy support for running init under the old-style initrd. Allows
+ the name linuxrc to act as init, and it doesn't assume init is PID 1.
+
+ This does not apply to initramfs, which runs /init as PID 1 and
+ requires no special support.
+
config BUSYBOX_CONFIG_FEATURE_USE_INITTAB
bool "Support reading an inittab file"
- default y
- depends on BUSYBOX_CONFIG_INIT
+ default BUSYBOX_DEFAULT_FEATURE_USE_INITTAB
+ depends on BUSYBOX_CONFIG_INIT || BUSYBOX_CONFIG_LINUXRC
help
Allow init to read an inittab file when the system boot.
config BUSYBOX_CONFIG_FEATURE_KILL_REMOVED
bool "Support killing processes that have been removed from inittab"
- default n
+ default BUSYBOX_DEFAULT_FEATURE_KILL_REMOVED
depends on BUSYBOX_CONFIG_FEATURE_USE_INITTAB
help
When respawn entries are removed from inittab and a SIGHUP is
config BUSYBOX_CONFIG_FEATURE_KILL_DELAY
int "How long to wait between TERM and KILL (0 - send TERM only)" if FEATURE_KILL_REMOVED
range 0 1024
- default 0
+ default BUSYBOX_DEFAULT_FEATURE_KILL_DELAY
depends on BUSYBOX_CONFIG_FEATURE_KILL_REMOVED
help
With nonzero setting, init sends TERM, forks, child waits N
config BUSYBOX_CONFIG_FEATURE_INIT_SCTTY
bool "Run commands with leading dash with controlling tty"
- default n
- depends on BUSYBOX_CONFIG_INIT
+ default BUSYBOX_DEFAULT_FEATURE_INIT_SCTTY
+ depends on BUSYBOX_CONFIG_INIT || BUSYBOX_CONFIG_LINUXRC
help
If this option is enabled, init will try to give a controlling
tty to any command which has leading hyphen (often it's "-/bin/sh").
config BUSYBOX_CONFIG_FEATURE_INIT_SYSLOG
bool "Enable init to write to syslog"
- default y
- depends on BUSYBOX_CONFIG_INIT
+ default BUSYBOX_DEFAULT_FEATURE_INIT_SYSLOG
+ depends on BUSYBOX_CONFIG_INIT || BUSYBOX_CONFIG_LINUXRC
config BUSYBOX_CONFIG_FEATURE_EXTRA_QUIET
bool "Be _extra_ quiet on boot"
- default n
- depends on BUSYBOX_CONFIG_INIT
+ default BUSYBOX_DEFAULT_FEATURE_EXTRA_QUIET
+ depends on BUSYBOX_CONFIG_INIT || BUSYBOX_CONFIG_LINUXRC
help
Prevent init from logging some messages to the console during boot.
config BUSYBOX_CONFIG_FEATURE_INIT_COREDUMPS
bool "Support dumping core for child processes (debugging only)"
- default n
- depends on BUSYBOX_CONFIG_INIT
+ default BUSYBOX_DEFAULT_FEATURE_INIT_COREDUMPS
+ depends on BUSYBOX_CONFIG_INIT || BUSYBOX_CONFIG_LINUXRC
help
If this option is enabled and the file /.init_enable_core
exists, then init will call setrlimit() to allow unlimited
core file sizes. If this option is disabled, processes
will not generate any core files.
-config BUSYBOX_CONFIG_FEATURE_INITRD
- bool "Support running init from within an initrd (not initramfs)"
- default n
- depends on BUSYBOX_CONFIG_INIT
- help
- Legacy support for running init under the old-style initrd. Allows
- the name linuxrc to act as init, and it doesn't assume init is PID 1.
-
- This does not apply to initramfs, which runs /init as PID 1 and
- requires no special support.
-
config BUSYBOX_CONFIG_INIT_TERMINAL_TYPE
string "Initial terminal type"
- default "linux"
- depends on BUSYBOX_CONFIG_INIT
+ default BUSYBOX_DEFAULT_INIT_TERMINAL_TYPE
+ depends on BUSYBOX_CONFIG_INIT || BUSYBOX_CONFIG_LINUXRC
help
This is the initial value set by init for the TERM environment
variable. This variable is used by programs which make use of
Note that on Linux, init attempts to detect serial terminal and
sets TERM to "vt102" if one is found.
+
+config BUSYBOX_CONFIG_FEATURE_INIT_MODIFY_CMDLINE
+ bool "Modify the command-line to \"init\""
+ default BUSYBOX_DEFAULT_FEATURE_INIT_MODIFY_CMDLINE
+ depends on BUSYBOX_CONFIG_INIT || BUSYBOX_CONFIG_LINUXRC
+ help
+ When launched as PID 1 and after parsing its arguments, init
+ wipes all the arguments but argv[0] and rewrites argv[0] to
+ contain only "init", so that its command-line appears solely as
+ "init" in tools such as ps.
+ If this option is set to Y, init will keep its original behavior,
+ otherwise, all the arguments including argv[0] will be preserved,
+ be they parsed or ignored by init.
+ The original command-line used to launch init can then be
+ retrieved in /proc/1/cmdline on Linux, for example.
config BUSYBOX_CONFIG_MESG
bool "mesg"
- default n
+ default BUSYBOX_DEFAULT_MESG
help
Mesg controls access to your terminal by others. It is typically
used to allow or disallow other users to write to your terminal
config BUSYBOX_CONFIG_FEATURE_MESG_ENABLE_ONLY_GROUP
bool "Enable writing to tty only by group, not by everybody"
- default n
+ default BUSYBOX_DEFAULT_FEATURE_MESG_ENABLE_ONLY_GROUP
depends on BUSYBOX_CONFIG_MESG
help
Usually, ttys are owned by group "tty", and "write" tool is
projects / openwrt / staging / chunkeey.git / blobdiff