FUSE integration #36

New Issue

A hack to access tahoe through FUSE has been committed to the "extensions" subdirectory in changeset:33a5f8ba6be39051. It isn't well-tested, but we have seen "find" and "cp" work! Thanks to nejucomo!

zooko commented

2008-01-04 19:33:12 +00:00

Whoops -- last night Seb and Josh and I tried out the FUSE extension, and it has bit-rotted. The first problem is that when you run it, it fails with a file-not-found error, but doesn't tell the user that she needs to put a directory uri ("cap") into that file. The second problem is that it expects the uri to be old style "DIR:" or "DIR-RO:", but nowadays they are all "DIR2:" or "DIR2-RO:". The third problem is that after changing it to expect "DIR2" instead of "DIR" then it fails with a message like "failed to initialize", which none of us knew how to diagnose.

Nej: if it isn't fixed by Sunday night I'm going to remove it from the source distribution for v0.7.0 release and replace it with a README and a hyperlink to a copy of it, unless you have a better idea.

Thanks!

Whoops -- last night Seb and Josh and I tried out the FUSE extension, and it has bit-rotted. The first problem is that when you run it, it fails with a file-not-found error, but doesn't tell the user that she needs to put a directory uri ("cap") into that file. The second problem is that it expects the uri to be old style "DIR:" or "DIR-RO:", but nowadays they are all "DIR2:" or "DIR2-RO:". The third problem is that after changing it to expect "DIR2" instead of "DIR" then it fails with a message like "failed to initialize", which none of us knew how to diagnose. Nej: if it isn't fixed by Sunday night I'm going to remove it from the source distribution for v0.7.0 release and replace it with a README and a hyperlink to a copy of it, unless you have a better idea. Thanks!

zooko added this to the 0.7.0 milestone 2008-01-04 19:34:03 +00:00

warner commented

2008-01-05 01:59:50 +00:00

I just moved the plugin from extensions/ to contrib/ . In most projects I'm familiar with, contrib/ is the place where they put stuff that might not work. I think it'd be sufficient and useful to leave it in place (with this "might not work" note) for 0.7.0, rather than removing it entirely. This way it's easy for someone else to find and hack on, perhaps they might fix it for us.

But feel free to remove it if you prefer.

I just moved the plugin from extensions/ to contrib/ . In most projects I'm familiar with, contrib/ is the place where they put stuff that might not work. I think it'd be sufficient and useful to leave it in place (with this "might not work" note) for 0.7.0, rather than removing it entirely. This way it's easy for someone else to find and hack on, perhaps they might fix it for us. But feel free to remove it if you prefer.

zooko commented

2008-01-05 02:35:31 +00:00

Okay, I'll leave it.

I'm still hoping nejucomo fixes it before I release 0.7.0...

Okay, I'll leave it. I'm still hoping nejucomo fixes it before I release 0.7.0...

zooko commented

2008-01-05 22:12:50 +00:00

Nejucomo says, on the phone, that the first argument to tahoe-fuse.py is the mount-point. So "failure to initialize" or whatever message that was we saw was probably just because we didn't pass any arguments.

Nejucomo says, on the phone, that the first argument to `tahoe-fuse.py` is the mount-point. So "failure to initialize" or whatever message that was we saw was probably just because we didn't pass any arguments.

zooko commented

2008-01-06 00:27:46 +00:00

arch_o_median is writing a test script for tahoe-fuse.py. :-)

zooko commented

2008-01-06 05:18:46 +00:00

arch_o_median: these are the things that the fuse extension needs for v0.7.0:

When you run it with no directory capability present, it prints out a message explaining that the thing that is missing is a read-only or a read-write directory capability, as well as the filename where that capability is supposed to be found.
When you run it with no arguments, it prints out a message saying that it requires an argument which is the mount point.
It works, for reading and writing files within the tahoe filesystem, copying files in and out, listing directories, moving files around within the tahoe filesystem, or at least for some subset of these operations. :-)

arch_o_median: these are the things that the fuse extension needs for v0.7.0: * When you run it with no directory capability present, it prints out a message explaining that the thing that is missing is a read-only or a read-write directory capability, as well as the filename where that capability is supposed to be found. * When you run it with no arguments, it prints out a message saying that it requires an argument which is the mount point. * It works, for reading and writing files within the tahoe filesystem, copying files in and out, listing directories, moving files around within the tahoe filesystem, or at least for some subset of these operations. :-)

zooko commented

2008-01-10 20:26:33 +00:00

nejucomo and I are going to work on this tomorrow after business hours.

tahoe-lafs added this to the undecided milestone 2008-01-23 02:26:54 +00:00

tahoe-lafs changed title from ~~FUSE integration~~ to FUSE integration (not specifically Windows)

2008-01-23 02:26:54 +00:00

zooko commented

2009-04-02 03:37:56 +00:00

See also more recent discussion about this on the mailing list: http://allmydata.org/pipermail/tahoe-dev/2008-November/000885.html

See also more recent discussion about this on the mailing list: <http://allmydata.org/pipermail/tahoe-dev/2008-November/000885.html>

zooko commented

2009-04-02 03:38:54 +00:00