;
-brkint ixoff -imaxbel
-icanon -echo
/scratch #
-Joe
-Original Message-
From: walter harms [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 14, 2007 1:34 AM
To: Joe Lau
Cc: 'busybox@busybox.net'
Subject: Re: no echo on shell
what das stty say ?
re,
wh
Joe Lau wrote:
On Busybox 1.6.1
= 0;
-brkint ixoff -imaxbel
-icanon -echo
/scratch #
-Joe
-Original Message-
From: walter harms [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 14, 2007 1:34 AM
To: Joe Lau
Cc: 'busybox@busybox.net'
Subject: Re: no echo on shell
what das stty say ?
re,
wh
Joe Lau wrote:
On Busybox
/scratch # - I typed the stty command here (but not echoed back by the
shell)
speed 9600 baud;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = undef;
eol2 = undef; swtch = undef; start = ^Q; stop = ^S; susp = ^Z; rprnt =
^R;
werase = ^W; lnext = ^V; flush = ^O; min
No, I did not kill any program or noticed any program died when this problem
happened.
-Joe
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Behalf Of Paul Fox
Sent: Monday, July 16, 2007 10:42 AM
To: busybox@busybox.net
Subject: Re: no echo on shell
/scratch
On Monday 16 July 2007 19:11, Joe Lau wrote:
No, I did not kill any program or noticed any program died when this problem
happened.
So how exactly this problem happens? Do you login thru
getty+login+ash on virtual console? or serial line? or over telnet?
or ssh?
Do you have any login scripts?
On Busybox 1.6.1 (more often) and 1.6.0, the shell (sh) can get into a mode
where it does not echo back the command that the user has entered.
The output from the command looks fine.
Has anyone run into this problem?
Thanks!
-Joe
___
busybox mailing
