9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "steve@quintile.net" <steve@quintile.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9P Cloud™
Date: Wed,  8 Jul 2015 07:09:36 +0100	[thread overview]
Message-ID: <438CD7D4-2C77-4B02-B9FB-6745A66A9E6E@quintile.net> (raw)
In-Reply-To: <CAFSF3XOi9CBixGZe+qyVGB-4hnObuge7JRsWU1OrY6YLGgCHvQ@mail.gmail.com>

not sure if this helps you, but cinap's cifsd in 9front works very well for me, exporting my plan9 file server to windows boxes.

-Steve





> On 8 Jul 2015, at 02:05, hiro <23hiro@gmail.com> wrote:
> 
> No, i mean the other way around: I would like to access the files in a
> real file browser (as if they were mounted like a network share).
> this mounting (and login) process should happen automatically at boot.
> 
> I currently do this for an sshfs share. A small arm computer does
> nothing else but exporting an sshfs mount to my local network (windows
> computers) via samba.
> 
> Also I would like to resume sharing my files with my friend after a
> reboot. So for uplink I'd also need automatic login.
> 
> On 7/8/15, Skip Tavakkolian <9nut@9netics.com> wrote:
>>> it would be useful to me if you would also create a second websocket
>>> server that accepts local samba file requests :)
>> 
>> integration with local and third party storage (Drive, S3, Dropbox)
>> are on the radar for future enhancements.
>> 
>> in the meantime, if you wanted to roll your own (in Go) ...
>> 
>> assuming i undrestand correclty -- that you want to export parts of
>> your SMB share via 9P Cloud to others -- you would need an oauth2
>> client that will authenticate itself then export a 9P filesystem over
>> websocket to 9pcloud.  you can use either goplan9 package at
>> https://github.com/9fans/go (rsc/rob) or go9p package at
>> https://code.google.com/p/go9p/ (lucho and andrey) for the 9p server
>> part and the oauth2 and websocket packages in Go repo on github for
>> authentication and websocket handling.  the javascript on the main
>> page should be helpful.
>> 
>> 
>> 



      reply	other threads:[~2015-07-08  6:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 18:00 Skip Tavakkolian
2015-07-07 18:59 ` a.regenfuss at gmx.de
2015-07-07 19:27 ` Wes Kussmaul
2015-07-07 22:11   ` Skip Tavakkolian
2015-07-07 23:30     ` hiro
2015-07-08  0:53       ` Skip Tavakkolian
2015-07-08  1:05         ` hiro
2015-07-08  6:09           ` steve [this message]

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=438CD7D4-2C77-4B02-B9FB-6745A66A9E6E@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).