Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


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

I crashed Linux



I had a case yesterday on a Tru64 Unix system where the X server 
locked out the mouse. We had focus on one screen, but somehow we 
managed to kill the window manager. I was able to telnet to his machine 
and kill the X server, which fixed the problem. 
On my home system, I have telnet and ftp turned off because my system 
was used as the gateway for my other computers, so it served as the 
firewall. If you are behind a firewall,  opening up telntet could give you a 
way to get into your system. 
On 7 Dec 2000, at 12:55, Derek Atkins wrote:

> This is a design flaw of the PC Architecture.  Other architectures
> have similar idiocies.  For example, on the Sun/Sparc architecture, if
> you unplug and then re-plug the keyboard into the CPU, the system will
> halt into the boot prom monitor, and you have to type "ok<return>" to
> get the system to continue running.

Jerry Feldman <gaf at blu.org>
Associate Director
Boston Linux and Unix user group
http://www.blu.org
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).




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

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org