aboutsummaryrefslogtreecommitdiff
path: root/init/init.c
diff options
context:
space:
mode:
authorGravatar Denys Vlasenko <vda.linux@googlemail.com>2017-07-21 09:50:55 +0200
committerGravatar Denys Vlasenko <vda.linux@googlemail.com>2017-07-21 09:50:55 +0200
commit72089cf6b4a77214ec4fd21d5ee5bf56958781cb (patch)
treea5cd9d8f47e909834d3dbc44f895556e68bcf18f /init/init.c
parent75d151e31d135ebab083307ded4e9b98970baa75 (diff)
downloadbusybox-72089cf6b4a77214ec4fd21d5ee5bf56958781cb.tar.gz
busybox-72089cf6b4a77214ec4fd21d5ee5bf56958781cb.tar.bz2
config: deindent all help texts
Those two spaces after tab have no effect, and always a nuisance when editing. Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Diffstat (limited to 'init/init.c')
-rw-r--r--init/init.c86
1 files changed, 43 insertions, 43 deletions
diff --git a/init/init.c b/init/init.c
index 3427e1cc8..ab137a981 100644
--- a/init/init.c
+++ b/init/init.c
@@ -14,34 +14,34 @@
//config: default y
//config: select FEATURE_SYSLOG
//config: help
-//config: init is the first program run when the system boots.
+//config: init is the first program run when the system boots.
//config:
//config:config LINUXRC
//config: bool "linuxrc: support running init from initrd (not initramfs)"
//config: default y
//config: select FEATURE_SYSLOG
//config: help
-//config: Legacy support for running init under the old-style initrd. Allows
-//config: the name linuxrc to act as init, and it doesn't assume init is PID 1.
+//config: Legacy support for running init under the old-style initrd. Allows
+//config: the name linuxrc to act as init, and it doesn't assume init is PID 1.
//config:
-//config: This does not apply to initramfs, which runs /init as PID 1 and
-//config: requires no special support.
+//config: This does not apply to initramfs, which runs /init as PID 1 and
+//config: requires no special support.
//config:
//config:config FEATURE_USE_INITTAB
//config: bool "Support reading an inittab file"
//config: default y
//config: depends on INIT || LINUXRC
//config: help
-//config: Allow init to read an inittab file when the system boot.
+//config: Allow init to read an inittab file when the system boot.
//config:
//config:config FEATURE_KILL_REMOVED
//config: bool "Support killing processes that have been removed from inittab"
//config: default n
//config: depends on FEATURE_USE_INITTAB
//config: help
-//config: When respawn entries are removed from inittab and a SIGHUP is
-//config: sent to init, this option will make init kill the processes
-//config: that have been removed.
+//config: When respawn entries are removed from inittab and a SIGHUP is
+//config: sent to init, this option will make init kill the processes
+//config: that have been removed.
//config:
//config:config FEATURE_KILL_DELAY
//config: int "How long to wait between TERM and KILL (0 - send TERM only)" if FEATURE_KILL_REMOVED
@@ -49,34 +49,34 @@
//config: default 0
//config: depends on FEATURE_KILL_REMOVED
//config: help
-//config: With nonzero setting, init sends TERM, forks, child waits N
-//config: seconds, sends KILL and exits. Setting it too high is unwise
-//config: (child will hang around for too long and could actually kill
-//config: the wrong process!)
+//config: With nonzero setting, init sends TERM, forks, child waits N
+//config: seconds, sends KILL and exits. Setting it too high is unwise
+//config: (child will hang around for too long and could actually kill
+//config: the wrong process!)
//config:
//config:config FEATURE_INIT_SCTTY
//config: bool "Run commands with leading dash with controlling tty"
//config: default y
//config: depends on INIT || LINUXRC
//config: help
-//config: If this option is enabled, init will try to give a controlling
-//config: tty to any command which has leading hyphen (often it's "-/bin/sh").
-//config: More precisely, init will do "ioctl(STDIN_FILENO, TIOCSCTTY, 0)".
-//config: If device attached to STDIN_FILENO can be a ctty but is not yet
-//config: a ctty for other session, it will become this process' ctty.
-//config: This is not the traditional init behavour, but is often what you want
-//config: in an embedded system where the console is only accessed during
-//config: development or for maintenance.
-//config: NB: using cttyhack applet may work better.
+//config: If this option is enabled, init will try to give a controlling
+//config: tty to any command which has leading hyphen (often it's "-/bin/sh").
+//config: More precisely, init will do "ioctl(STDIN_FILENO, TIOCSCTTY, 0)".
+//config: If device attached to STDIN_FILENO can be a ctty but is not yet
+//config: a ctty for other session, it will become this process' ctty.
+//config: This is not the traditional init behavour, but is often what you want
+//config: in an embedded system where the console is only accessed during
+//config: development or for maintenance.
+//config: NB: using cttyhack applet may work better.
//config:
//config:config FEATURE_INIT_SYSLOG
//config: bool "Enable init to write to syslog"
//config: default y
//config: depends on INIT || LINUXRC
//config: help
-//config: If selected, some init messages are sent to syslog.
-//config: Otherwise, they are sent to VT #5 if linux virtual tty is detected
-//config: (if not, no separate logging is done).
+//config: If selected, some init messages are sent to syslog.
+//config: Otherwise, they are sent to VT #5 if linux virtual tty is detected
+//config: (if not, no separate logging is done).
//config:
//config:config FEATURE_INIT_QUIET
//config: bool "Be quiet on boot (no 'init started:' message)"
@@ -88,37 +88,37 @@
//config: default n # not Y because this is a debug option
//config: depends on INIT || LINUXRC
//config: help
-//config: If this option is enabled and the file /.init_enable_core
-//config: exists, then init will call setrlimit() to allow unlimited
-//config: core file sizes. If this option is disabled, processes
-//config: will not generate any core files.
+//config: If this option is enabled and the file /.init_enable_core
+//config: exists, then init will call setrlimit() to allow unlimited
+//config: core file sizes. If this option is disabled, processes
+//config: will not generate any core files.
//config:
//config:config INIT_TERMINAL_TYPE
//config: string "Initial terminal type"
//config: default "linux"
//config: depends on INIT || LINUXRC
//config: help
-//config: This is the initial value set by init for the TERM environment
-//config: variable. This variable is used by programs which make use of
-//config: extended terminal capabilities.
+//config: This is the initial value set by init for the TERM environment
+//config: variable. This variable is used by programs which make use of
+//config: extended terminal capabilities.
//config:
-//config: Note that on Linux, init attempts to detect serial terminal and
-//config: sets TERM to "vt102" if one is found.
+//config: Note that on Linux, init attempts to detect serial terminal and
+//config: sets TERM to "vt102" if one is found.
//config:
//config:config FEATURE_INIT_MODIFY_CMDLINE
//config: bool "Clear init's command line"
//config: default y
//config: depends on INIT || LINUXRC
//config: help
-//config: When launched as PID 1 and after parsing its arguments, init
-//config: wipes all the arguments but argv[0] and rewrites argv[0] to
-//config: contain only "init", so that its command line appears solely as
-//config: "init" in tools such as ps.
-//config: If this option is set to Y, init will keep its original behavior,
-//config: otherwise, all the arguments including argv[0] will be preserved,
-//config: be they parsed or ignored by init.
-//config: The original command-line used to launch init can then be
-//config: retrieved in /proc/1/cmdline on Linux, for example.
+//config: When launched as PID 1 and after parsing its arguments, init
+//config: wipes all the arguments but argv[0] and rewrites argv[0] to
+//config: contain only "init", so that its command line appears solely as
+//config: "init" in tools such as ps.
+//config: If this option is set to Y, init will keep its original behavior,
+//config: otherwise, all the arguments including argv[0] will be preserved,
+//config: be they parsed or ignored by init.
+//config: The original command-line used to launch init can then be
+//config: retrieved in /proc/1/cmdline on Linux, for example.
//applet:IF_INIT(APPLET(init, BB_DIR_SBIN, BB_SUID_DROP))
//applet:IF_LINUXRC(APPLET_ODDNAME(linuxrc, init, BB_DIR_ROOT, BB_SUID_DROP, linuxrc))