BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Recovering Corrupted Bash Shell

Subject: Recovering Corrupted Bash Shell
From: kristian.hermansen at gmail.com (Kristian Hermansen)
Date: Sat, 24 Feb 2007 23:45:30 -0500
In-reply-to: <45E113A1.1020308@thekramers.net>
References: <fe37588d0702242035l5bfbf010xffa837f9b51d1684@mail.gmail.com> <45E113A1.1020308@thekramers.net>

On 2/24/07, David Kramer <david at thekramers.net> wrote:
> The most likely cause of this is non-printable characters being sent to
> the shell that happen to match control characters that configure it.

RIght...but which characters?

> The most likely fix is to run the command "stty sane".

That did not work...
-- 
Kristian Hermansen

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Follow-Ups:
- Recovering Corrupted Bash Shell
  - From: david at thekramers.net (David Kramer)

References:
- Recovering Corrupted Bash Shell
  - From: kristian.hermansen at gmail.com (Kristian Hermansen)
- Recovering Corrupted Bash Shell
  - From: david at thekramers.net (David Kramer)

Prev by Date: Recovering Corrupted Bash Shell
Next by Date: Recovering Corrupted Bash Shell
Previous by thread: Recovering Corrupted Bash Shell
Next by thread: Recovering Corrupted Bash Shell
Index(es):
- Date
- Thread


BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Boston Linux & Unix / webmaster@blu.org