9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Export local plumber to remote unix host?
Date: Wed, 27 Aug 2008 23:57:51 +0800	[thread overview]
Message-ID: <140e7ec30808270857k4df5b110x25f4b13255b9e3c2@mail.gmail.com> (raw)
In-Reply-To: <1219823269-sup-1399@neocybil.x1024.net>

On Wed, Aug 27, 2008 at 4:02 PM, Jon Dugan <jdugan@x1024.net> wrote:
> What I'd like
> to be able to do is export at least my plumber over the ssh connection to the
> remote host so I can display the attachments locally.  This seems to be the
> opposite of what import(1) does.  I guess what I want is cpu(1) for
> plan9port...  or at least a limited version of it.
>
> Any suggestions?  (Unfortunately the Unix boxes and Word documents aren't
> going away any time soon for me...)

 You have two problems here:
1) Accessing plan 9's plumber from unix
2) Accessing unix files (attachments) from plan 9

 1 isn't too difficult, a listen1 with exportfs -r /mnt/plumb combined
with an ssh port forward (-L or -R, can't remember which applies here)
will give you access to the plumber via p9p's 9p (probably in
combination with srv -a for authentication).
 2 is a little more problematic. It's easy enough to run u9fs over ssh
(see srvssh), but the caveat is when you plumb an attachment like say
/home/jon/mail/foo.doc the plumber running on plan 9 is going to go
"/home? wtf is that?". As long as you can devise a convention to get
around that you should be good to go.

 Of course, seems like it might be a bit simpler to run acme Mail.
-sqweek



  reply	other threads:[~2008-08-27 15:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-27  8:02 Jon Dugan
2008-08-27 15:57 ` sqweek [this message]
2008-08-27 16:11   ` erik quanstrom
2008-08-27 16:53   ` sqweek
2008-08-27 17:53 ` a

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=140e7ec30808270857k4df5b110x25f4b13255b9e3c2@mail.gmail.com \
    --to=sqweek@gmail.com \
    --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).