From: Dan Kegel <dank@kegel.com>
To: sun-zj <sun-zj@tdk-tech.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: cant't stop program
Date: Sun, 04 Jan 2004 20:11:52 -0800 [thread overview]
Message-ID: <3FF8E408.8060507@kegel.com> (raw)
In-Reply-To: <200401050235.UAA05095@lists.linuxppc.org>
sun-zj wrote:
> After the denk's instruction, I can run the
> linuxppc-2.4.23 on PPC8xx without too much difficulty. But when running some
> programming , I want to terminate it like I do on PC by press Ctrl+C.
> It doesn't work at all :(. It can work under the U-boot environment. I
> wonder whether this is the
> problem of Linux os Or Kermit?
I have seem problems like that when running from serial
console under Busybox. I think busybox's init is buggy.
Does the problem happen when you telnet in from another computer,
or only on a serial console?
- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-05 4:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 2:33 cant't stop program sun-zj
2004-01-05 4:11 ` Dan Kegel [this message]
2004-01-05 15:51 ` Jaap-Jan Boor
2004-01-06 2:25 ` Jon Masters
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=3FF8E408.8060507@kegel.com \
--to=dank@kegel.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sun-zj@tdk-tech.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).