From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: Date: Sat, 11 Oct 2008 13:11:24 +0200 From: "Rudolf Sykora" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_93840_20477507.1223723484593" References: <6c8648266ca7da5d844043386b740ac2@quanstro.net> Subject: Re: [9fans] bug in rio: unhiding deleted windows Topicbox-Message-UUID: 1bd5627a-ead4-11e9-9d60-3106f5b1d025 ------=_Part_93840_20477507.1223723484593 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 2008/10/11 Russ Cox > Rather than litter the kernel with special case code, > why not just set up your terminal to listen to the network? > Then if you get in that state again you can drawterm in. > > Russ > > Again, I am normally (with my notebook) _NOT_ connected to _ANY_ network. Yet, I still dare want to be at least able to stop the filesystem when sth. like that happens again. (If I can do it elsewhere -- in linux I don't remember the case I could do nothing -- unless I set and make the keybord unfuctional ...) Ruda ------=_Part_93840_20477507.1223723484593 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline


2008/10/11 Russ Cox <rsc@swtch.com>
Rather than litter the kernel with special case code,
why not just set up your terminal to listen to the network?
Then if you get in that state again you can drawterm in.

Russ

Again, I am normally (with my notebook) _NOT_ connected to _ANY_ network.
Yet, I still dare want to be at least able to stop the filesystem when sth. like that happens again.
(If I can do it elsewhere -- in linux I don't remember the case I could do nothing -- unless I set and make the keybord unfuctional ...)
Ruda
------=_Part_93840_20477507.1223723484593--