[cap-talk] ANNOUNCING Allmydata.org "Tahoe", the Least-Authority Filesystem, v1.1
Rob Meijer
capibara at xs4all.nl
Sat Jun 28 10:45:07 CDT 2008
Very interesting.
It seems that your Tahoe project and my MinorFs project while sharing some
basic concepts, both focus on areas that the other projects largely
ignore.
Tahoe seems to mostly focus on the distributed aspects, while MinorFs
focuses on the local aspects. And where Fuse is the base building block
for MinorFs, for Tahoe it is secondary only.
I feel that it, given the sharing of concepts and differences in focus,
might be interesting to explore if and how MinorFs and Tahoe could either
work together smoothly, or could possibly even converge into a single
project.
Zooko, could I ask you to look at the basic setup for MinorFs at
http://polacanthus.net/review/appendixb.pdf (I just put up an updated
version of this document that addresses administrative needs not addressed
in previous designs, the new design has however not yet propagated to the
current codebase), and see if such efforts would be have potential of
being fruitful ?
To others on the list I would like to ask if efforts to let Tahoe and
MinorFs cooperate would have the potential to yield something more usefull
than the two separate projects ?
Rob J Meijer
On Tue, June 24, 2008 17:12, zooko wrote:
> On Jun 11, 2008, at 11:29 PM, Rob Meijer wrote:
>
>>> http://allmydata.org/source/tahoe/trunk/docs/about.html
>>
>> I just skimmed some of the pages.
>> I see two technologies mentioned, that I until now assumed
>> incompatible.
> ...
>> Fuse user space file system library/kernel module.
> ...
>> Cygwin
> ...
>> Given such possibilities, I would very
>> much like to investigate if my MinorFs project also could possibly
>> be made
>> portable to Cygwin/Windows in such a way.
>
> The FUSE interface doesn't work on cygwin, but Tahoe (LAFS) can be
> used through other interfaces.
>
> The standard way to use Tahoe right now is the "wapi" (which I
> pronounce "wappy"): [1] . The wapi is a RESTful interface and comes
> with a free wui ("wooey").
>
> The FUSE interface is of great interest to many people, apparently,
> but it is not mature. (There are three separate implementations,
> none of which has good test coverage.)
>
> Another good way to use Tahoe would be through the "foolscap" secure
> remote object protocol. Foolscap is modelled on the E remote object
> protocol. It is implemented only in Python.
>
> Of these, only the FUSE ones don't work on cygwin.
>
> Regards,
>
> Zooko
>
> [1] http://allmydata.org/trac/tahoe/browser/docs/webapi.txt
> _______________________________________________
> cap-talk mailing list
> cap-talk at mail.eros-os.org
> http://www.eros-os.org/mailman/listinfo/cap-talk
>
>
More information about the cap-talk
mailing list