[package] fix breakage on wl500gp after r18214, thanks sn9 (#6084)

[openwrt.git] / package / busybox / config / init / Config.in

diff --git a/package/busybox/config/init/Config.in b/package/busybox/config/init/Config.in
index 6e3bf9d..75f3298 100644 (file)
--- a/package/busybox/config/init/Config.in
+++ b/package/busybox/config/init/Config.in
@@ -12,14 +12,6 @@ config BUSYBOX_CONFIG_INIT
        help
          init is the first program run when the system boots.
 
        help
          init is the first program run when the system boots.
 

-config BUSYBOX_CONFIG_DEBUG_INIT
-       bool "Debugging aid"
-       default n
-       depends on BUSYBOX_CONFIG_INIT
-       help
-         Turn this on to disable all the dangerous
-         rebooting stuff when debugging.
-

 config BUSYBOX_CONFIG_FEATURE_USE_INITTAB
        bool "Support reading an inittab file"
        default y
 config BUSYBOX_CONFIG_FEATURE_USE_INITTAB
        bool "Support reading an inittab file"
        default y


@@ -40,11 +32,12 @@ 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
        int "How long to wait between TERM and KILL (0 - send TERM only)" if FEATURE_KILL_REMOVED
        range 0 1024
        default 0

+       depends on BUSYBOX_CONFIG_FEATURE_KILL_REMOVED

        help
          With nonzero setting, init sends TERM, forks, child waits N
          seconds, sends KILL and exits. Setting it too high is unwise
        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!)
+         (child will hang around for too long and could actually kill
+         the wrong process!)

 
 config BUSYBOX_CONFIG_FEATURE_INIT_SCTTY
        bool "Run commands with leading dash with controlling tty"
 
 config BUSYBOX_CONFIG_FEATURE_INIT_SCTTY
        bool "Run commands with leading dash with controlling tty"


@@ -80,17 +73,15 @@ config BUSYBOX_CONFIG_FEATURE_INIT_COREDUMPS
        help
          If this option is enabled and the file /.init_enable_core
          exists, then init will call setrlimit() to allow unlimited
        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
+         core file sizes. If this option is disabled, processes

          will not generate any core files.
 
          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
 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
+         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
          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


@@ -106,7 +97,7 @@ config BUSYBOX_CONFIG_MESG
        bool "mesg"
        default y
        help
        bool "mesg"
        default y
        help

-         Mesg controls access to your terminal by others.  It is typically
+         Mesg controls access to your terminal by others. It is typically

          used to allow or disallow other users to write to your terminal
 
 endmenu
          used to allow or disallow other users to write to your terminal
 
 endmenu