9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] ape sockets and plan9
Date: Tue, 28 Dec 2010 20:02:58 -0800	[thread overview]
Message-ID: <AANLkTikig6BVSrDotCm-_hJevtGxdjq+BUX4fDZtVjz5@mail.gmail.com> (raw)
In-Reply-To: <c937e433f70d5ce11a11d360c4713a4d@plug.quanstro.net>

Sorry, I'm tired, long day, but this discussion is not making sense to
me. I hope I don't make anyone mad at me :-)

9vx can accept connections today, with or without the ether device.
I've used 9vx to export root file systems to ARMs. It's how I
bootstrapped my openrd.

Now, there is this business in Unix called privileged ports. If you
want to export port 564, then you must run 9vx as root. Problem
solved.

Listen1 is quite fun and handy for this kind of tinkering around.
Also, you can trace all the 9vx network activity on many unixes:
strace -etrace=network 9vx etc. etc.
And see where things go sour.

The only issue is that if your 9vx host is using a port (e.g. 22) then
9vx can't export on that port, because the 9vx port space and the host
os port space are shared.

As for 9vx forks on bitbucket: we're all good with hierarchical name
spaces, right? I mean, yiyus/9vx and rminnich/9vx are not the same
thing. I'm not usually in a hurry to pull from yiyus, because I've
felt no urgency to do so, If you want me to try something, let me
know.

Bitbucket has worked very well for me across a lot of projects. So has
hg in general. They're both great, and they work well from Plan 9.
Don't like em? Don't use 'em ;-)

ron



  parent reply	other threads:[~2010-12-29  4:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-25  5:06 Fernan Bolando
2010-12-25 17:04 ` Steve Simon
2010-12-25 19:41   ` Bakul Shah
2010-12-28 13:23     ` Fernan Bolando
2010-12-28 16:34       ` erik quanstrom
2010-12-28 17:41         ` Devon H. O'Dell
2010-12-28 18:39           ` Bakul Shah
2010-12-28 18:50             ` erik quanstrom
2010-12-28 19:45               ` Bakul Shah
2010-12-29  4:02               ` ron minnich [this message]
2011-01-01  1:36                 ` Fernan Bolando
2011-01-01 14:59                   ` erik quanstrom
2011-01-01 15:28                   ` ron minnich

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=AANLkTikig6BVSrDotCm-_hJevtGxdjq+BUX4fDZtVjz5@mail.gmail.com \
    --to=rminnich@gmail.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).