From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9Cloud Source
Date: Thu, 17 Mar 2016 01:16:43 +0000 [thread overview]
Message-ID: <CAJSxfmKbb9Np152KS6DnKhbiMCrkwsMJUa3mqQFsYW_rbUD6HQ@mail.gmail.com> (raw)
In-Reply-To: <CAJSxfmLvMiNcCTwPqd4aiVBfi5b1z1OdXJJeXAHoDKoLhm7z5A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1653 bytes --]
I couldn't find it on 9p.io, so I'm not sure what happened. I recall that I
screwed up the first two attempts and had to ask David to clean them up for
me.
Anyhow, I submitted the patch to Labs' sources a few minutes ago:
/n/sources/patch/syscall-exportfs
On Wed, Mar 16, 2016 at 5:18 PM Skip Tavakkolian <skip.tavakkolian@gmail.com>
wrote:
> i mean "syscall-exportfs"
>
>
> On Wed, Mar 16, 2016 at 5:10 PM Skip Tavakkolian <
> skip.tavakkolian@gmail.com> wrote:
>
>> i submitted the patch to 9p.io some time ago; it was under
>> "syscall-exprotfs".
>>
>>
>> On Wed, Mar 16, 2016 at 4:16 PM hiro <23hiro@gmail.com> wrote:
>>
>>> Hello Skip, is there a way I could receive the patch for export?
>>>
>>> On 7/15/15, Skip Tavakkolian <9nut@9netics.com> wrote:
>>> > assuming you mean 9PCloud (otherwise ignore this):
>>> >
>>> > i plan to put the 9P javascript sources on github or bitbucket. you
>>> > can view the sources using the debugger in chrome. they're all
>>> > dual-licensed (MIT and GPLv2). i also plan to make a simple version
>>> > of the namespace "janitor" (brucee coined the term) that uses factotum
>>> > handle auth. it will be in the same source repo.
>>> >
>>> > the backend uses a custom Plan 9 cpu that includes the "export"
>>> > (exportfs) system call. the patch for export was submitted to all
>>> > fronts, popular or otherwise (Labs, 9p.io, 9atom, 9front).
>>> >
>>> >> Hi guys,
>>> >>
>>> >> Was wondering if the source of 9Cloud was available for perusal? Just
>>> >> logged in, looks great!
>>> >>
>>> >> Many thanks!
>>> >>
>>> >> Shane.
>>> >
>>> >
>>> >
>>>
>>>
[-- Attachment #2: Type: text/html, Size: 2849 bytes --]
next prev parent reply other threads:[~2016-03-17 1:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 21:57 Shane Morris
2015-07-15 21:35 ` Skip Tavakkolian
2015-07-15 23:04 ` Shane Morris
2015-07-16 6:36 ` Skip Tavakkolian
2016-03-16 23:16 ` hiro
2016-03-17 0:10 ` Skip Tavakkolian
2016-03-17 0:18 ` Skip Tavakkolian
2016-03-17 1:16 ` Skip Tavakkolian [this message]
2016-03-17 11:57 ` arisawa
2016-03-17 12:03 ` David du Colombier
2016-03-17 11:58 ` David du Colombier
2016-03-18 21:52 ` Skip Tavakkolian
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=CAJSxfmKbb9Np152KS6DnKhbiMCrkwsMJUa3mqQFsYW_rbUD6HQ@mail.gmail.com \
--to=skip.tavakkolian@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).