[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Wishlist for woody+1

On Sun, May 26, 2002 at 10:38:53PM -0400, Joey Hess wrote:
> Brian May wrote:
> > My problem I always have with init=/bin/sh (not sure if emergency mode
> > helps or not), is that I always forget that Ctrl+C doesn't work...
> init=/usr/bin/screen
> Well, I've not tried that, but as I also suffer from the ctrl-c problem
> (being unable to kill ping *sucks*), I always remember to run screen
> immediatly. And I recently learned that if you make screen your login
> shell, it will run /bin/sh in it for you.
> > Any ideas how to enable Ctrl+C to prevent mishaps like this?
> I suppose magic sysreq could be used. I'd like to know why ctrl-c fails
> too tho.

Run a getty by hand, or use `open' (openvt now?).  Init starts on
//dev/console, not dev/tty1, which is much like not having a
/controlling terminal at all; thus no signals from the user to the
terminal's foreground process group get delivered properly.

Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer

To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: