9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] sam/rc script problem
Date: Tue, 16 Dec 2008 13:08:17 +0000	[thread overview]
Message-ID: <1295100d9db84ab0e50f470ef38221ff@quintile.net> (raw)
In-Reply-To: <a560a5d00812160425g2cc7b8a3u11eb7f1ea85c47b2@mail.gmail.com>

> 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



  parent reply	other threads:[~2008-12-16 13:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16 12:25 Rudolf Sykora
2008-12-16 13:02 ` lucio
2008-12-16 13:08 ` Steve Simon [this message]
2008-12-16 14:00   ` erik quanstrom
2008-12-16 14:13     ` gdiaz
2008-12-16 16:22       ` Rudolf Sykora
2008-12-16 16:38         ` erik quanstrom
2008-12-16 16:56           ` Rudolf Sykora
2008-12-16 17:29             ` Martin Neubauer
2008-12-16 14:05   ` Charles Forsyth
2008-12-16 19:25   ` Rudolf Sykora
2008-12-16 19:29     ` erik quanstrom
2008-12-16 19:43     ` michael block
2008-12-16 20:14       ` Rudolf Sykora
2008-12-16 17:18 ` Russ Cox
2008-12-16 17:28   ` Rudolf Sykora
2008-12-16 17:31     ` erik quanstrom
2008-12-16 17:48       ` Rudolf Sykora
2008-12-16 18:13         ` erik quanstrom
2008-12-16 18:38           ` Charles Forsyth

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=1295100d9db84ab0e50f470ef38221ff@quintile.net \
    --to=steve@quintile.net \
    --cc=9fans@9fans.net \
    /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).