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

Jan Engelhardt, le Mon 19 Jun 2006 14:08:28 +0200, a écrit :
> >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`),

That's equivalent to the "emergency" mode.

Samuel
-
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/

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

Prev by Date: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
Next by Date: Re: [RFC] [PATCH 5/8] inode-diet: Eliminate i_blksize and use a per-superblock default
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]