From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9Term settings
Date: Thu, 5 Dec 2002 01:44:20 -0500 [thread overview]
Message-ID: <dba54f360d7bfe3b8827f74f9f485fec@plan9.bell-labs.com> (raw)
> | My Question is how can I run plan9 and still communicate
> | properly. Currently I can connect and type but can`t use
> | programs such as vi. Any thoughts, comments or suggestions
> | greatly appreciated.
>
> Use sam instead of vi!
Or use u9fs!
Compiling u9fs is one of the first things I do every time
I get a new Unix account. I run it over ssh through some
convoluted hoops that I've recently packaged into srvssh (see srv(4)).
This way it runs as you talking to your SSH connection, rather than as
a dedicated daemon listening to the network at large.
Combined with this plumbing rule:
type is text
data matches 'Local (.*)'
plumb to none
plumb start rc -c $1
and I'm all set. I type "Local 9fs linux" in an acme window,
button-2 click it, button-3 click it, and now it's mounted
in my acme namespace as well as any rio windows I draw thereafter.
Russ
g% cat /usr/rsc/bin/rc/9fs # [names below changed to protect the innocent.]
#!/bin/rc
switch($1){
case spade
srvssh -r -u /home/rsc/u9fs/u9fs spade.demon.com spade /n/spade
case eecs
srvssh -r -u /home/soda/rsc/u9fs/u9fs soda.eecs.berkeley.edu eecs /n/eecs
case 18.404
srvssh -r -u /home/18.404/bin/u9fs 18.404@courses.athena.mit.edu 18.404 /n/18.404x &&
bind /n/18.404x/home/18.404 /n/18.404
case linux
srvssh -r -u /home/rsc/u9fs/u9fs linux
case ord
srvssh -r ord.lcs.mit.edu ord /n/ord
case sfo
srvssh -r sfo.lcs.mit.edu sfo /n/sfo
case ewr
srvssh -r -u /home/ny3/rsc/bin/FreeBSD/i386/u9fs ewr.lcs.mit.edu ewr /n/ewr
case *
exec /rc/bin/9fs $*
}
exit ''
g%
next reply other threads:[~2002-12-05 6:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-05 6:44 Russ Cox [this message]
2002-12-05 6:53 ` rob pike
-- strict thread matches above, loose matches on Subject: below --
2002-12-01 15:29 nowayjose
[not found] <athiele@charter.net>
2002-12-01 15:26 ` Adrian
2002-12-02 0:31 ` Scott Schwartz
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=dba54f360d7bfe3b8827f74f9f485fec@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).