Re: emergency or init=/bin/sh mode and terminal signals

>Hi,
>
>There's a long-standing issue in init=/bin/sh mode: pressing control-C
>doesn't send a SIGINT to programs running on the console. The incurred
>typical pitfall is if one runs ping without a -c option... no way to
>stop it!

Worse, I can observe same behavior when using "-b", i.e. init=/sbin/init 
called with -b (read: `/sbin/init -b`), and init starts a su shell before 
continuing. No ^C either to my knowledge.
rpm -q sysvinit: 2.86


Jan Engelhardt
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: emergency or init=/bin/sh mode and terminal signals
    • From: Samuel Thibault <[email protected]>

• References:
  • emergency or init=/bin/sh mode and terminal signals
    • From: Samuel Thibault <[email protected]>

• Prev by Date: Re: Several errors in kernel
• Next by Date: Re: [PATCHSET] Announce: High-res timers, tickless/dyntick and dynamic HZ
• Previous by thread: Re: emergency or init=/bin/sh mode and terminal signals
• Next by thread: Re: emergency or init=/bin/sh mode and terminal signals
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]