From: Mark Chambers <markc@mail.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Control-C in bash ???
Date: Tue, 14 Jan 2003 08:44:09 -0500 [thread overview]
Message-ID: <200301140844.09234.markc@mail.com> (raw)
In-Reply-To: <20030113193102.E7B7CC608E@atlas.denx.de>
Thanks for your help on this one. I changed the last line of etc/inittab to
3:2345:respawn:/sbin/mingetty --noclear tts/0
and added "tts/0" to etc/securetty and now I get a console with job control.
I don't know how long it would have taken me to discover "job control" or "controlling tty"!!
(I'm learning linux from the ground up)
Thanks again,
Mark Chambers
Original message:
> On a PC, I can, for instance, enter "ping 192.168.1.4", then hit Control-C and
> stop the ping. For the life of me, I can't figure out how to do the same on
> my MPC860 system!!!
> I have an MPC860 running 2.4.19, with a mostly unmodified eldk distribution
> from Wolfgang Denx. I did modify the init script to use /dev/console instead
> of /ttyx (standard driver using SMC1). I'd not only like a solution, I want
> to undertand how this works - I've poked around and I can't figure out what's
> supposed to happen - Is the shell that generates a SIGINT, or the uart
> driver, or what? Any enlightenment will be greatly appreciated...
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-14 13:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 19:09 Control-C in bash ??? Mark Chambers
2003-01-13 19:20 ` Der Herr Hofrat
2003-01-13 19:30 ` Wolfgang Denk
2003-01-14 13:44 ` Mark Chambers [this message]
2003-01-13 19:48 ` Chris Wedgwood
2003-01-14 13:31 ` Alex Zeffertt
2003-01-14 14:50 ` Wolfgang Denk
2003-01-14 14:51 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2003-01-13 19:16 Kerl, John
2003-01-13 19:39 ` Mark Chambers
2003-01-13 19:25 Kerl, John
2003-01-13 19:59 Kerl, John
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200301140844.09234.markc@mail.com \
--to=markc@mail.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.