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: [email protected] Subject: Re: no echo on shell > /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 = 1; time = 0; > -brkint ixoff -imaxbel > -icanon -echo ^^^^^ this is the problem. someone is turning off echo, and it's not getting turned back on. are you perhaps killing off a program (e.g., using ^C), that might have disabled character echo? such a program _should_ catch the interrupt signal, in order to restore the tty the way it found it, but many do not. in the meantime, "stty echo" will reenable echo. a good command to use is "stty sane", which restores most (all?) of the default tty settings. paul =--------------------- paul fox, [EMAIL PROTECTED] _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox _______________________________________________ busybox mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/busybox
