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



John Chambers <jc at trillian.mit.edu> writes:

> Too bad the keyboard and mouse cables never have those little  screws
> like  the  monitor  has  that  prevents fallout.  Of course, the real
> idiocy here is that plugging the mouse back in didn't make  it  start
> working again. I'd guess that's probably a hardward idiocy, though it
> is probably exacerbated by some matching software idiocy.

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.

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/      PP-ASEL      N1NWH
       warlord at MIT.EDU                        PGP key available
-
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