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: david at thekramers.net (David Kramer)
Date: Sun, 25 Feb 2007 00:29:09 -0500
In-reply-to: <fe37588d0702242045n1b61b80j41de5266d94d2216@mail.gmail.com>
References: <fe37588d0702242035l5bfbf010xffa837f9b51d1684@mail.gmail.com> <45E113A1.1020308@thekramers.net> <fe37588d0702242045n1b61b80j41de5266d94d2216@mail.gmail.com>

Kristian Hermansen wrote:
> 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?

I couldn't find a comprehensive list, but this is the kind of stuff I'm
taking about:
http://www.ibb.net/~anne/keyboard/troubleshooting.html
https://www.redhat.com/archives/rpm-list/2003-December/msg00175.html
http://lists.debian.org/debian-user/1997/09/msg00358.html

-- 
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: kristian.hermansen at gmail.com (Kristian Hermansen)

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

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