| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103 |
- #
- # For a description of the syntax of this configuration file,
- # see scripts/kbuild/config-language.txt.
- #
- menu "Init Utilities"
- config BUSYBOX_INIT
- bool "init"
- default y
- select BUSYBOX_FEATURE_SYSLOG
- help
- init is the first program run when the system boots.
- config BUSYBOX_FEATURE_USE_INITTAB
- bool "Support reading an inittab file"
- default y
- depends on BUSYBOX_INIT
- help
- Allow init to read an inittab file when the system boot.
- config BUSYBOX_FEATURE_KILL_REMOVED
- bool "Support killing processes that have been removed from inittab"
- default y
- depends on BUSYBOX_FEATURE_USE_INITTAB
- help
- When respawn entries are removed from inittab and a SIGHUP is
- sent to init, this feature will kill the processes that have
- been removed.
- config BUSYBOX_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
- help
- With nonzero setting, init sends TERM, forks, child waits N
- seconds, sends KILL and exits. Setting it too high is unwise
- (child will hang around for too long and can actually kill
- wrong process!)
- config BUSYBOX_FEATURE_INIT_SCTTY
- bool "Run commands with leading dash with controlling tty"
- default n
- depends on BUSYBOX_INIT
- 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").
- More precisely, init will do "ioctl(STDIN_FILENO, TIOCSCTTY, 0)".
- If device attached to STDIN_FILENO can be a ctty but is not yet
- a ctty for other session, it will become this process' ctty.
- This is not the traditional init behavour, but is often what you want
- in an embedded system where the console is only accessed during
- development or for maintenance.
- NB: using cttyhack applet may work better.
- config BUSYBOX_FEATURE_INIT_SYSLOG
- bool "Enable init to write to syslog"
- default y
- depends on BUSYBOX_INIT
- config BUSYBOX_FEATURE_EXTRA_QUIET
- bool "Be _extra_ quiet on boot"
- default n
- depends on BUSYBOX_INIT
- help
- Prevent init from logging some messages to the console during boot.
- config BUSYBOX_FEATURE_INIT_COREDUMPS
- bool "Support dumping core for child processes (debugging only)"
- default n
- depends on BUSYBOX_INIT
- 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.
- # you should never need this, breaks allconfig images
- #config BUSYBOX_FEATURE_INITRD
- # bool "Support running init from within an initrd (not initramfs)"
- # default n
- # depends on BUSYBOX_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_HALT
- bool "poweroff, halt, and reboot"
- default y
- help
- Stop all processes and either halt, reboot, or power off the system.
- config BUSYBOX_MESG
- bool "mesg"
- default n
- help
- Mesg controls access to your terminal by others. It is typically
- used to allow or disallow other users to write to your terminal
- endmenu
|
