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

linux-os (Dick Johnson), le Mon 19 Jun 2006 07:37:02 -0400, a écrit :
> I don't think this is the correct behavior. You can't allow some
> terminal input to affect init. It has been the de facto standard
> in Unix, that the only time one should have a controlling terminal
> is after somebody logs in and owns something to control. If you want
> a controlling terminal from your emergency shell, please exec /bin/login.

Ok, but people don't know that: they're given a shell, and wonder why on
hell ^C doesn't work...

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/

---

• Follow-Ups:
  • Re: emergency or init=/bin/sh mode and terminal signals
    • From: "linux-os \(Dick Johnson\)" <[email protected]>
  • Re: emergency or init=/bin/sh mode and terminal signals
    • From: "linux-os \(Dick Johnson\)" <[email protected]>

• 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: "linux-os \(Dick Johnson\)" <[email protected]>

• Prev by Date: Re: [patch] increase spinlock-debug looping timeouts from 1 sec to 1 min
• Next by Date: Re: [PATCH 16/16] 64bit Resource: finally enable 64bit resource sizes
• 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]