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

Albert Cahalan, le Sun 18 Jun 2006 23:47:51 -0400, a écrit :
> Samuel Thibault writes:
> 
> >The attached patch sets such session and controlling tty up, which fixes
> >the issue. The unfortunate effect is that init might be killed if one
> >presses control-C very fast after its start.
> 
> Doesn't the kernel protect process 1 from any signal
> that it does not have a handler for?

Ah, yes, indeed, forgot that.

> I think there is no problem.

Agreed.

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:
  • Re: emergency or init=/bin/sh mode and terminal signals
    • From: "Albert Cahalan" <[email protected]>

• Prev by Date: Re: [discuss] Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
• Next by Date: Re: [PATCH 4/7] fuse: add POSIX file locking support
• Previous by thread: Re: emergency or init=/bin/sh mode and terminal signals
• Next by thread: [PATCH 1/1] i4l: Gigaset drivers: add IOCTLs to compat_ioctl.h
• 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]