From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] tcp access to (fake worm) fs?
Date: Mon, 2 Sep 2002 22:12:59 -0400 [thread overview]
Message-ID: <a6485a281906e6942a3ffc5e465bade2@plan9.bell-labs.com> (raw)
On your cpu server, running
aux/listen1 tcp!*!9fs /bin/aux/trampoline il!your-file-server!9fs &
should set up a tunnel, so that you can pretend
your CPU server is a tcp version of your file server.
You can also put
#!/bin/rc
exec aux/trampoline il!your-file-server!9fs
into /rc/bin/service/tcp564, if you want to
use listen instead.
Russ
next reply other threads:[~2002-09-03 2:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 2:12 Russ Cox [this message]
2002-09-03 8:56 ` Axel Belinfante
2002-09-03 14:50 ` [9fans] rio on the authentication server Brian Hancock
-- strict thread matches above, loose matches on Subject: below --
2002-09-02 20:07 [9fans] tcp access to (fake worm) fs? Axel Belinfante
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=a6485a281906e6942a3ffc5e465bade2@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).