From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from c716099-a.rchdsn1.tx.home.com ([24.7.105.70] helo=ignatious) by speech.braille.uwo.ca with esmtp (Exim 3.32 #1 (Debian)) id 15h99X-0001B6-00 for ; Wed, 12 Sep 2001 08:30:03 -0400 Received: from cpt.kirk (helo=localhost) by ignatious with local-esmtp (Exim 3.12 #1 (Debian)) id 15h9Zt-0003mj-00 for ; Wed, 12 Sep 2001 07:57:17 -0500 Date: Wed, 12 Sep 2001 07:57:17 -0500 (CDT) From: Kirk Wood X-Sender: cpt.kirk@ignatious To: speakup@braille.uwo.ca Subject: Re: regaining crashed consoles In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: speakup-admin@braille.uwo.ca Errors-To: speakup-admin@braille.uwo.ca X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: speakup@braille.uwo.ca List-Help: List-Post: List-Subscribe: , List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: On Wed, 12 Sep 2001, Shaun Oliver wrote: > ok, in that case, what the hell do you do when your keyboard won't > responde to anything. This shouldn't happen often. And unfortunately, there has been no foolproof means of recovery. If this happens regularly, something is major wrong with your system. And that goes for all regardless of system. I cringe when people say that it is normal for winblows to lock. It is not normal. While it is very true that winblows is not nearly as stable, and it is true that (most versions) require regular restarting to regain lost resources, it shouldn't regularly lock. ======= Kirk Wood Cpt.Kirk@1tree.net The mind is like a parachute; it works much better when open. If you're too open minded, your brains will fall out.