9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Pietro Gagliardi <pietro10@mac.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Getting drawterm to work in Leopard (again)
Date: Thu, 19 Jun 2008 18:24:43 -0400	[thread overview]
Message-ID: <2AD4903F-B13C-4DB9-B676-53295F96C189@mac.com> (raw)
In-Reply-To: <5ef1ca87ddf8a8c1c4a3f5c5cb0d71f5@quanstro.net>

All the ports except the guard and ticket (56[67]) work, and AS is
still botched, so I believe AS has to do with one of those two (most
likely ticket. This port problem might have to do with OS X. I'll ask
around.

On Jun 19, 2008, at 2:50 PM, erik quanstrom wrote:

>> Hello. I'm trying to get drawterm to work in Leopard again. Here is
>> my
>> command line:
>>
>> 	drawterm-osx-intel -c 'tcp!127.0.0.1!17010' -a 'tcp!127.0.0.1!
>> 2567' -
>> s 'tcp!127.0.0.1!5356' -u pietro
>>
>> The problem was that it told me the connection refused. I told the
>> firewall to open ports 17010, 2567, and 5356, and I got "AS protocol
>> botch" after entering my password. I then told it to open all ports
>> 1-32768, and QEMU failed to start.
>>
>> What are the correct ports? Thanks.
>
> ; for(i in guard ticket secstore exportfs rexexec cpu)
> 	ndb/query tcp $i
> tcp=guard port=566
> tcp=ticket port=567
> tcp=secstore port=5356
> tcp=exportfs port=17007
> tcp=rexexec port=17009
> tcp=cpu port=17013
>
> the easiest way to derive this information is by looking in /rc/bin/
> service
> and eliminating the ones you know aren't used.
>
> btw, this command line is equivalent:
>
> 	drawtern-osx-intel -c 127.0.0.1 -a 127.0.0.1
>
> - erik
>
>




  reply	other threads:[~2008-06-19 22:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-19 18:08 Pietro Gagliardi
2008-06-19 18:50 ` erik quanstrom
2008-06-19 22:24   ` Pietro Gagliardi [this message]
2008-06-19 22:33     ` erik quanstrom
2008-06-19 22:40     ` Federico G. Benavento
2008-06-20  7:35     ` Jeff Sickel
2008-06-19 20:51 ` Iruata Souza

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=2AD4903F-B13C-4DB9-B676-53295F96C189@mac.com \
    --to=pietro10@mac.com \
    --cc=9fans@9fans.net \
    /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).