From: Jeff Sickel <jas@spamisham.corpus-callosum.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sshnet usage?
Date: Wed, 11 Dec 2002 16:56:16 +0000 [thread overview]
Message-ID: <uveq1381rm13a2@corp.supernews.com> (raw)
In-Reply-To: <b201d47b8865e79dfe9dc8ca4e8654ed@plan9.bell-labs.com>
Russ Cox <rsc@plan9.bell-labs.com> wrote:
> No, I was just confused about how transparent you
> wanted the tunnel to be. As long as you only need the
> tunnel to be one way, this is easy.
> Basically, if you do
> sshnet hop1
> mntgen
> srvssh hop2
> (assuming u9fs is in your path on hop2),
> that posts the u9fs service in /srv/hop2,
> so that then running
> mntgen
> 9fs hop2
Thanks.
This is exactly what I was wanting to do. So much more to learn...
Jeff
next prev parent reply other threads:[~2002-12-11 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 15:49 Russ Cox
2002-12-11 16:56 ` Jeff Sickel [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-11 14:00 Russ Cox
2002-12-11 14:47 ` Jeff Sickel
2002-12-11 9:52 Jeff Sickel
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=uveq1381rm13a2@corp.supernews.com \
--to=jas@spamisham.corpus-callosum.com \
--cc=9fans@cse.psu.edu \
/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).