CTRL-C - Make the hurting stop
Jason Farque
JasonF at pigging.com
Fri Dec 7 13:39:17 PST 2007
I think I finally figured this out.
My particular problem was that I was running rcS like this (busybox rcS
default):
::sysinit:/etc/init.d/rcS
Running rcS like that places the output on console rather than ttyS0.
This fixes that:
ttyS0::sysinit:/etc/init.d/rcS
Now I can ctrl-c rcS and my follow-on boot script(s).
Jason
-----Original Message-----
From: Lombard, David N [mailto:dnlombar at ichips.intel.com]
Sent: Friday, December 07, 2007 3:18 PM
To: Jason Farque
Cc: busybox at busybox.net
Subject: Re: CTRL-C - Make the hurting stop
On Fri, Dec 07, 2007 at 02:06:51PM -0600, Jason Farque wrote:
> David,
>
> Yes, I'm running a serial console at 38400 baud on ttyS0.
I meant system console, as in "console=ttyS0,38400n8" on the kernel
command
line...
> 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:
Hmmm. cttyhack doesn't do:
setsid()
ioctl(0,TIOCSCTTY,1)
kboot <http://kboot.sourceforge.net> has a utils/getctty.c that may be
the very thing you want.
--
David N. Lombard, Intel, Irvine, CA
I do not speak for Intel Corporation; all comments are strictly my own.
More information about the busybox
mailing list