CTRL-C - Make the hurting stop

[Jason Farque]

David,

Yes, I'm running a serial console at 38400 baud on ttyS0.  What I expect
to work but does not is:

::respawn:/usr/bin/cttyhack /usr/ash

The message " cttyhack: switching to '/dev/ttyS0'" comes right at the
tail end of the boot process, after /etc/init.d/rcS has executed.  I
need to be able to ctrl-c out of my rcS and/or the program(s) that it
executes.  Perhaps the system is working as intended but my linux boot
sequence knowledge is too weak.  What I'm trying to do is:

System boot
Kernel load
rcS -> calls my boot script
boot script executes my data logger executable
executable runs forever unless I ctrl-c for debugging purposes

I cannot break out of my executable that has been run at the end of my
boot script.  Is there a better, more proper and more fully functional
way of performing this boot sequence?

Could I sneak a peek at your functioning inittab?

Thanks,

Jason


-----Original Message-----
From: Lombard, David N [mailto:dnlombar at ichips.intel.com] 
Sent: Friday, December 07, 2007 1:56 PM
To: Jason Farque
Cc: busybox at busybox.net
Subject: Re: CTRL-C - Make the hurting stop

On Fri, Dec 07, 2007 at 12:44:38PM -0600, Jason Farque wrote:
> Well known issue I realize, but I can't ctrl-c in my ttyS0 terminal
> window because it's not a controlling tty.  I've tried the methods of
> using getty, using cttyhack, and modifying ctty.c all to no avail.
I've
> read all that I can google up about it and have tried various
> work-arounds all to no avail.  I still can't ctrl-c in my terminal
with
> busybox 1.8.2.
> 
> I'm on a MIPS au1550 embedded system, big endian, using 2.6.12 linux
> kernel.  What I want is for Busybox 1.8.2 (which compiles and runs
fine)
> to simply boot to a root command prompt on my system without a login
> prompt the way that my old Busybox 1.2.2.1 does.

Hmmm.  Are you running with a serial console?  I do, and it all works
as expected.

Some keys, like <Ctrl-U> required CONFIG_FEATURE_EDITING_FANCY_KEYS=y,
but <Ctrl-C> does not.  BTW this is handled in libbb/lineedit.c

Note also that some config item names changed between 1.2 and 1.8, did
you account for that?

-- 
David N. Lombard, Intel, Irvine, CA
I do not speak for Intel Corporation; all comments are strictly my own.