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] ssh v2, using a remote linux server
Date: Sun,  3 May 2009 07:56:34 -0700	[thread overview]
Message-ID: <dd6fe68a0905030756q5e04dda6r3dfc4267251e8a63@mail.gmail.com> (raw)
In-Reply-To: <a560a5d00905030726j54bd5aa1q54c53b845c0bd7ff@mail.gmail.com>

> 2)
> More generally:
> I use a powerful linux machine for doing some havier calculations. I
> have no possibility of changing anything serious on that computer
> (like that it could serve ssh v1), I am just an ordinary user. So far
> I usually do the programming on my 'local' linux computer using p9p
> versions of acme & rc (sometimes the linux's gvim), run some small
> manageable tests on this local computer, then make a copy to the
> remote machine, recompile it there (fortran) using a textual ssh
> connection, and finally run it there. This brings along a /number of
> complications... It'd be nicer if I could use the remote linux machine
> in a way a plan9 cpu server is used. Is this possible?

When you're developing on the big machine,
you could mount the big machine's file system
locally, and then you can continue to use acme
to edit.  If you want to use 9p, you could add
the -e flag to srv and then use u9fs over ssh + 9pfuse.
Alternately, if you have fuse installed you could
use sshfs instead (Linux tool, not p9p tool).

This way you mount the remote machine on /n/big
and set things up so that the remote machine
sends back path names like /n/big/home/you,
so things like plumbing continue to work just fine.
(Instead of awd in your cd alias (see label(1)), you'd
use label /n/big`pwd`/-big.)

Russ


  reply	other threads:[~2009-05-03 14:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-03 14:26 Rudolf Sykora
2009-05-03 14:56 ` Russ Cox [this message]
2009-05-04 20:30   ` Steve Simon
2009-05-05  7:50     ` maht
2009-05-03 15:09 ` john
2009-05-03 17:28 ` lucio

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=dd6fe68a0905030756q5e04dda6r3dfc4267251e8a63@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).