From: Uriel <uriell@binarydream.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] p9sk2
Date: Tue, 4 Oct 2005 23:10:52 +0100 [thread overview]
Message-ID: <20051004221052.GE19776@server4.lensbuddy.com> (raw)
In-Reply-To: <ee9e417a0510041444r5158b04dq6291af24fe4609f8@mail.gmail.com>
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
next prev parent reply other threads:[~2005-10-04 22:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 21:04 Uriel
2005-10-04 21:16 ` Axel Belinfante
2005-10-04 21:30 ` Axel Belinfante
2005-10-04 21:38 ` Uriel
2005-10-04 21:48 ` Skip Tavakkolian
2005-10-04 21:44 ` Russ Cox
2005-10-04 21:52 ` andrey mirtchovski
2005-10-04 22:05 ` geoff
2005-10-04 22:28 ` andrey mirtchovski
2005-10-04 22:38 ` Skip Tavakkolian
2005-10-04 22:41 ` Russ Cox
2005-10-04 22:42 ` andrey mirtchovski
2005-10-04 22:10 ` Uriel [this message]
2005-10-04 23:21 ` Skip Tavakkolian
2005-10-04 23:26 ` Russ Cox
2005-10-04 23:35 ` Russ Cox
2005-10-05 0:11 ` Uriel
2005-10-05 0:19 ` Russ Cox
2005-10-05 0:22 ` Skip Tavakkolian
2005-10-05 1:27 ` Uriel
2005-10-05 1:50 ` Russ Cox
2005-10-05 2:13 ` jmk
2005-10-05 4:56 ` LiteStar numnums
2005-10-24 13:52 ` Uriel
2005-10-24 14:17 ` jmk
[not found] ` <000001c5c94e$82d49890$14aaa8c0@utelsystems.local>
2005-10-05 5:36 ` Nils O. Selåsdal
2005-10-04 23:36 ` David Leimbach
2005-10-05 7:20 ` Richard Miller
2005-10-05 7:44 ` Skip Tavakkolian
[not found] ` <67a09890a59797f569b0456bb3edcc86@hamnavoe.com>
2005-10-05 10:46 ` Russ Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051004221052.GE19776@server4.lensbuddy.com \
--to=uriell@binarydream.org \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).