From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <1295100d9db84ab0e50f470ef38221ff@quintile.net>
From: "Steve Simon" <steve@quintile.net>
Date: Tue, 16 Dec 2008 13:08:17 +0000
To: 9fans@9fans.net
In-Reply-To: <a560a5d00812160425g2cc7b8a3u11eb7f1ea85c47b2@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] sam/rc script problem
Topicbox-Message-UUID: 62a390b4-ead4-11e9-9d60-3106f5b1d025

> P.S.: Is there anything more intelligent than 'vt' for connecting to a
> linux machine?

It all depends what you want to run on the linux box.

if you need VT in order to run your editor you could edit the file remotely
from plan9. To do this either run u9fs on the linux box, or pick up
sftpfs from contrib and use ssh. You can then import your linux boxes
namespace from plan9 (by convention put the magic in the 9fs script so its easy to do).

now you can edit files and run normal command line tools on plan9, and you only
need to use your ssh session to start programs. this (in my case at least) means I
no longer need vt and just use a rio window, so all the features of rio work
in the linx windows as elsewhere.

beware, bash can do some strange things to its output as you cut and paste long lines to it.
I usually run either a Bourne shell or Byron's rc(1) for Unix for sanity's sake.

if you get into this then you might like to take a look at rwd(1) which tries to keep
your local 'current dir' in sync with the remote one, allowing the plumber and
and filename completion to work.

It is very satisfying being able to plumb errors from a remote invocation of
gcc and see the file appear in sam on plan9.

-Steve