From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <140e7ec30808270857k4df5b110x25f4b13255b9e3c2@mail.gmail.com> Date: Wed, 27 Aug 2008 23:57:51 +0800 From: sqweek To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> In-Reply-To: <1219823269-sup-1399@neocybil.x1024.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1219823269-sup-1399@neocybil.x1024.net> Subject: Re: [9fans] Export local plumber to remote unix host? Topicbox-Message-UUID: 08efdc4e-ead4-11e9-9d60-3106f5b1d025 On Wed, Aug 27, 2008 at 4:02 PM, Jon Dugan 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