[tahoe-dev] fuse status.

Nathan nejucomo at gmail.com
Fri Jan 11 20:49:22 UTC 2008


Hi folks,

The release announcement for 0.7.0 mentioned the fuse interface which
is a contribution I submitted during the second AllMyData hackfest.  I
wrote this as a proof-of-concept, in a very quick'n'dirty fashion, and
I hadn't touched it since that hackfest until this week when I noticed
the announcement.

Sad to say, it does not appear at all to work.  Two things changed
since then:  The tahoe code base, and the python-fuse wrapper.  I
suspect the latter of altering the semantics and interface between
releases, but have not confirmed this.


Basically, I cut'n'pasted a python-fuse example, adding a best-guess
for how to map that to the tahoe WAPI.

Then I iterated this process:

a. run the fuse plugin
b. try some file system operation
c. if this operation seemed to succeed, pick a different operation and
go to step b.
d. stop the fuse plugin.
e. modify the source code. (usually guessing what the file system
layer or user process expected the result to be, rather than refering
to docs.  Sometimes running a similar op on ext3.)
f. go to step a.

To note are that there is no automated test process, as for most of
tahoe-proper, and it is not based on any good reference
specifications.  In other words caveat emptor.  I believe 0.7.0 is
quite usable via the web interface and command line client, but the
current tahoe-fuse.py contribution is woefully "experimental".


I'll take a look at it this weekend and see if I can't get it working
with a HowTo setup/run doc.


Nejucomo



More information about the tahoe-dev mailing list