From: Stanley Lieber <stanley.lieber@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] exportfs / u9fs / v9fs / npfs / spfs versus 9vx
Date: Thu, 12 May 2011 14:11:57 -0500 [thread overview]
Message-ID: <BANLkTinGM8UT8HczpJN12BMGJNx0FJercw@mail.gmail.com> (raw)
In-Reply-To: <20110512190313.GA14768@clanspum.net>
On Thu, May 12, 2011 at 2:03 PM, Daniel Lyons <fusion@storytotell.org> wrote:
> On Thu, May 12, 2011 at 11:52:30AM -0700, Bakul Shah wrote:
>> On Thu, 12 May 2011 13:14:55 CDT Stanley Lieber <stanley.lieber@gmail.com> wrote:
>> > http://plan9.bell-labs.com/sources/plan9/sys/src/cmd/unix/u9fs
>> >
>> > This is the basis of the OpenBSD port.
>>
>> unix/9pfreebsd is really too old to be useful but may be one
>> can start a new FreeBSD port from the openBSD bits? I'd be
>> interested in such a thing.
>
> It compiles w/ 2 warning messages on my machine. Setting it up is
> turning out to be interesting. I think probably the safest thing for
> me to do would be to try tunnelling it over ssh, since both host
> operating systems can do ssh v2. Still hammering on it. It does look
> like 9vx isn't really able to talk to the machine from here, which is
> odd because p9p's srv seems to be able to, at least make the
> connection, though I'm not having much luck with that either.
>
> How are you guys using these tools?
I connect to unix machines from Plan 9 by installing fgb/openssh
from contrib, binding /386/bin/openssh over /bin, and then using srvssh.
The command line looks something like this:
srvssh sl@phoenix phoenix && 9fs phoenix
This mounts u9fs running as user sl on host phoenix in /n/phoenix.
Alternately, taruti's scpu (ssh2 client written in go) can be used:
srv -s 5 'scpu -u sl -h phoenix -notty -c u9fs -u sl -na none' phoenix
/n/phoenix
scpu is available here:
https://bitbucket.org/taruti/scpu
-sl
next prev parent reply other threads:[~2011-05-12 19:11 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 16:49 Daniel Lyons
2011-05-12 18:13 ` Lyndon Nerenberg
2011-05-12 18:14 ` Stanley Lieber
2011-05-12 18:52 ` Bakul Shah
2011-05-12 19:03 ` Daniel Lyons
2011-05-12 19:11 ` Stanley Lieber [this message]
2011-05-12 19:17 ` andrey mirtchovski
2011-05-13 23:00 ` Daniel Lyons
2011-05-14 2:47 ` andrey mirtchovski
2011-05-14 6:02 ` Daniel Lyons
2011-05-14 7:59 ` Charles Forsyth
2011-05-16 16:22 ` Yaroslav
2011-05-12 20:30 ` Bakul Shah
2011-05-12 20:53 ` Daniel Lyons
2011-05-12 23:45 ` Iruatã Souza
2011-05-12 23:47 ` Iruatã Souza
2011-05-16 6:48 ` Bakul Shah
2011-05-16 12:18 ` Iruatã Souza
2011-05-12 19:58 ` Anthony Sorace
2011-05-12 21:04 ` Steve Simon
2011-05-12 22:33 ` Anthony Sorace
2011-05-21 7:21 ` Steve Simon
2011-05-12 22:03 ` 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=BANLkTinGM8UT8HczpJN12BMGJNx0FJercw@mail.gmail.com \
--to=stanley.lieber@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).