9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9vx as a cpu server?
Date: Sun,  1 Feb 2009 20:27:04 -0800	[thread overview]
Message-ID: <dd6fe68a0902012027s158fbd38m32be0fedae5587af@mail.gmail.com> (raw)
In-Reply-To: <d7eaa4c2839da98e11bb2d1c6a88ce08@smgl.fr.eu.org>

On Sun, Feb 1, 2009 at 10:19 AM, Mathieu <lejatorn@gmail.com> wrote:
> Hello,
>
> Simple question: how hard would it be to modify 9vx so it can be used
> as a cpu server?
>
> As I naively see it, the two main problems are:
> 1) to have 9vx running a cpu server kernel instead of a stand alone
> terminal one (I don't even know if that's the case actually).
> 2) to have the host forwarding whatever packets should go to 9vx.
>
> I had two goals in mind; obviously being able to have a cpu server
> without having to dedicate another machine for that at home, but also
> I will need to run some tests over the net for an app I will try to
> write and that will require to have several plan 9 hosts being able to
> talk to each other.
> I realize vmware could cut it, but I find 9vx much easier to use, so I
> was wondering if that would be at all possible...

you don't need a cpu server kernel to be a cpu server.
the main difference between the two kernels is which
startup script (termrc or cpurc) gets run.  if you start
the listeners, you can be a cpu server.

as for listening, 9vx by default uses the host ip stack,
and plan 9 services tend to use their own port numbers,
so as long as you don't want, say, to split ssh to your
host away from ssh to your 9vx instance, you should
be able to just use the stock 9vx and run "aux/listen tcp".

of course, 9vx is running as an ordinary linux user,
which means that the concept of user when accessing
the local file system will not be meaningful -- everyone
will have the access of the user who started 9vx.

russ


  parent reply	other threads:[~2009-02-02  4:27 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 [this message]
2009-02-02 16:29   ` Roman V. Shaposhnik
2009-02-02 16:54     ` roger peppe
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=dd6fe68a0902012027s158fbd38m32be0fedae5587af@mail.gmail.com \
    --to=rsc@swtch.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).