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

[linux-os (Dick Johnson)]

On Mon, 19 Jun 2006, Samuel Thibault wrote:

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

Actually, a rather trivial program can be written, the name of
which you define as init on the command-line 'init=/bin/myprog'.
This program sets up the controlling terminal, then exec()s
/bin/bash or whatever shell you want. Since it's exec()ed, the
PID remains at 1 so after you have fixed whatever you needed
to fix, you can execute `exec /sbin/init auto` and continue
with a normal startup. This is certainly cleaner than poking
holes in the kernel.

Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.4 on an i686 machine (5592.72 BogoMips).
New book: http://www.AbominableFirebug.com/
_


****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@xxxxxxxxxxxx - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/