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

Hi,

Willy Tarreau, le Sun 18 Jun 2006 23:33:42 +0200, a écrit :
> I too am used to starting with init=/bin/sh, but I'm also used to launch
> ping in the background. However, if getting Ctrl-C working implies a risk
> of killing init, then I'd rather keep it the old way.

Maybe you should rather use init=/bin/login . If your login program is
smart enough, it will set a session and thus ^C will 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]>

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: Willy Tarreau <[email protected]>

Prev by Date: Re: [patch 8/8] lock validator: add s390 to supported options
Next by Date: Re: emergency or init=/bin/sh mode and terminal signals
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]