From: "Bill J.Xu" <xujz@neusoft.com>
To: Charles Lepple <clepple@ghz.cc>, linux-kernel@vger.kernel.org
Subject: Re: "ctrl+c" disabled!
Date: Fri, 22 Aug 2003 12:55:48 +0800 [thread overview]
Message-ID: <05a501c36869$a7aeee60$2a01010a@avwindows> (raw)
In-Reply-To: bi45b6$kor$1@sea.gmane.org
Yeah,that is the result after pressing ctrl+c, ctrl+d. maybe od do not get the "ctrl+c" signal.
But I use SecureCRT with the same configration at the same PC to telnet the linux box,everything is OK.
So I think that if there is some thing wrong with linux kernel?
Bill
----- Original Message -----
From: "Charles Lepple" <clepple@ghz.cc>
To: <linux-kernel@vger.kernel.org>
Sent: Friday, August 22, 2003 12:14 PM
Subject: Re: "ctrl+c" disabled!
> Bill J.Xu wrote:
> > after run od -tx1, the following is the result
> > ------------------------------------------------
> > bash-2.05# ./od -tx1
> > 0000000
>
> That's after you pressed ^C in your terminal program? What you have
> there shows that od has not received any characters.
>
> Pick another control character, and use 'stty intr' to set that as your
> interrupt character. I don't have any experience with SecureCRT, but it
> may use ^C to implement the Windows Edit->Copy function.
>
> --
> Charles Lepple <ghz.cc!clepple>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-08-22 4:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-21 12:30 "ctrl+c" disabled! Bill J.Xu
2003-08-21 12:46 ` Richard B. Johnson
2003-08-22 1:50 ` Bill J.Xu
2003-08-22 13:16 ` Richard B. Johnson
2003-08-22 2:04 ` Edgar Toernig
2003-08-22 2:12 ` Bill J.Xu
2003-08-22 2:42 ` Edgar Toernig
2003-08-22 3:22 ` Bill J.Xu
2003-08-22 4:14 ` Charles Lepple
2003-08-22 4:55 ` Bill J.Xu [this message]
2003-08-22 11:27 ` Russell King
2003-08-22 13:22 ` Edgar Toernig
2003-09-01 4:50 ` Bill J.Xu
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='05a501c36869$a7aeee60$2a01010a@avwindows' \
--to=xujz@neusoft.com \
--cc=clepple@ghz.cc \
--cc=linux-kernel@vger.kernel.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.