From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 4 Oct 2005 23:10:52 +0100 From: Uriel To: 9fans@cse.psu.edu Subject: Re: [9fans] p9sk2 Message-ID: <20051004221052.GE19776@server4.lensbuddy.com> References: <20051004210425.GC19776@server4.lensbuddy.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Topicbox-Message-UUID: 94699b06-ead0-11e9-9d60-3106f5b1d025 On Tue, Oct 04, 2005 at 05:44:04PM -0400, Russ Cox wrote: > > I was trying to document -O in cpu(1) which is undocumented, it enables > > It is like -R (run the server aka remote side of the protocol) > except that it runs the pre-9P2000 server side. > It is undocumented because you never say it yourself > on the command line (just like -R) I'm not sure that just because you don't call it directly it means that it should not be documented, you still need to use some times, see: http://plan9.bell-labs.com/wiki/plan9/Drawterm_to_your_terminal/ > and because it needs to go away. It persists only because of > drawterm. On that I will agree. > > My guess is that it's needed for drawterm to be able to connect, will dt2k > > fix that? what is up with dt2k anyway? > > As it always is, progress is slow. Skip and Brucee have added Windows > support to dt2k, and Andrey has been maintaining it. I use it for days > at a time without problems on Linux except that snarf doesn't work. > Others have reported problems. At the moment, it's really far down > on my to do list, and no one else is stepping up to the plate. First one would have to find the source... wasn't drawterm(2k) supposed to move to sources? I know f2f had the source in his site, but it's not linked from anywhere, and I can't recall the address, and that was a while ago, so who knows if the code is up to date? The stuff in /sys/src/cmd/unix/drawterm looks quite outdated. uriel