From: roger peppe <rogpeppe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9vx as a cpu server?
Date: Mon, 2 Feb 2009 16:54:40 +0000 [thread overview]
Message-ID: <df49a7370902020854q72986c5sbc73004ad1366b05@mail.gmail.com> (raw)
In-Reply-To: <1233592196.4412.250.camel@goose.sun.com>
why hasn't that old unix restriction been removed yet?
is there any point to it at all any more?
localhost-only announcing i suppose.
2009/2/2 Roman V. Shaposhnik <rvs@sun.com>:
> On Sun, 2009-02-01 at 20:27 -0800, Russ Cox wrote:
>> as for listening, 9vx by default uses the host ip stack,
>> and plan 9 services tend to use their own port numbers,
>
> And sometimes these port # tend to be < 1024 which means that
> you have to run 9vx as root.
>
> Thanks,
> Roman.
>
>
>
next prev parent reply other threads:[~2009-02-02 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 18:19 Mathieu
2009-02-01 18:29 ` erik quanstrom
2009-02-01 21:29 ` Mathieu
2009-02-01 21:40 ` Devon H. O'Dell
2009-02-02 4:27 ` Russ Cox
2009-02-02 16:29 ` Roman V. Shaposhnik
2009-02-02 16:54 ` roger peppe [this message]
2009-02-02 17:07 ` ron minnich
2009-02-02 17:10 ` erik quanstrom
2009-02-02 19:11 ` Charles Forsyth
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=df49a7370902020854q72986c5sbc73004ad1366b05@mail.gmail.com \
--to=rogpeppe@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).