This is a discussion on Avoiding a trashed /dev/tty within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> Every now and then, while running dosemu in a shell, I can run something that crashes dosemu in a ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Every now and then, while running dosemu in a shell, I can run something that crashes dosemu in a way that freezes the linux tty. If I then restart the tty with a kill -9 <pid of hung shell> from another shell, I do get a Login: prompt back, but its a dead end! Anything I type creates a blurb of high/low ascii characters that are uninterpretable/unseen by the cmd processor (ie. one can not escape to any other tty using alt-Fn or ctrl-c or ctrl-alt-del, etc.). I was wondering if something like embedding a reset command in my /etc/profile would be the correct way to go? TonyB |
| ||||
| Hufnus wrote: > > Anything I type creates a blurb of high/low ascii characters > that are uninterpretable/unseen by the cmd processor (ie. one > can not escape to any other tty using alt-Fn or ctrl-c or > ctrl-alt-del, etc.). > > I was wondering if something like embedding a reset command in > my /etc/profile would be the correct way to go? Did you try to just type: reset Even if you can't read the command you type it should reset the tty to a sane state, unless your key bindings have been changed too by the crashed program. Regards, Kees. -- Kees Theunissen. |
| Thread Tools | |
| Display Modes | |
|
|