From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: From: "Russ Cox" To: 9fans@cse.psu.edu Subject: Re: [9fans] 9Term settings MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Date: Thu, 5 Dec 2002 01:44:20 -0500 Topicbox-Message-UUID: 2dc22aa8-eacb-11e9-9e20-41e7f4b1d025 > | 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%