[BusyBox] RFC: giving respawn init actions a controlling tty?

[Quy Tonthat]

Erik Andersen wrote:

>Currently the busybox init code assumes that "respawn" init
>actions are non-interactive, and therefore should not get a
>controlling tty.  This works fine when people use respawn to
>launch a getty or syslogd or some such thing.  However, we are
>increasingly seeing people try to launch ash, or bash, or minicom
>or midnight commander or some other interactive application.
>Since launching an interactive application using "respawn" does
>not provide a controlling tty, we then get people complaining
>that job control was disabled and similar problems.
>
>I see two ways to solve this.  We can either give people a
>controlling tty for "respawn" init actions, or we can create a
>new type of init action, (i.e. "interactive-respawn") that does
>provide a controlling tty.  Thoughts?
>
> -Erik
>  
>
Or using openvt applet I submitted few weeks ago.

Quy