I ran grep and it ended up reading a binary file. Now my console is
gibberish -- control chars, escape sequences, and non-printable chars.
I tried kill -HUP on getty, I tried kill on getty -- no dice. Any
ideas?
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL
hi, logout and login again
Paul
On Thu, 14 Aug 1997, Shaleh wrote:
I ran grep and it ended up reading a binary file. Now my console is
gibberish -- control chars, escape sequences, and non-printable chars.
I tried kill -HUP on getty, I tried kill on getty -- no dice. Any
ideas?
--
You can try reset, tput reset and echo ^V^O. I have had most success with
echo ^V^O
I Hope this helps.
// Heikki
Shaleh wrote:
I ran grep and it ended up reading a binary file. Now my console is
gibberish -- control chars, escape sequences, and non-printable chars.
I tried kill -HUP on
hi, logout and login again
Paul
That might not be enough to fix it. If it's still hosed, try running
'reset' this is usually enough to clear-up most situations like this.
Note: you may have to type it in blind since you won't be able to
see the text as you're typing it. Also, I don't
Try the reset command. I believe the best results are when TERM=linux,
but I can't be sure.
Brandon
On Thu, 14 Aug 1997, Shaleh wrote:
I ran grep and it ended up reading a binary file. Now my console is
gibberish -- control chars, escape sequences, and non-printable chars.
I tried kill
-
- hi, logout and login again
- Paul
-
- On Thu, 14 Aug 1997, Shaleh wrote:
-
- I ran grep and it ended up reading a binary file. Now my console is
- gibberish -- control chars, escape sequences, and non-printable chars.
- I tried kill -HUP on getty, I tried kill on getty -- no dice.
6 matches
Mail list logo