Config.in 6.9 KB

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