tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

Q: FUSE? A: YES! 

[Imported from Trac: page FAQ, version 61]
zooko 2012-01-23 05:48:07 +00:00
parent 3763dfa779
commit 2c9b2bdfce
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
FAQ.md

@ -152,3 +152,8 @@ the break-even point at which the LIT filecap is the same length as a typical CH
* [*pipermail/tahoe-dev/2010-April/004235.html Storing a small file leads to a weird read capability] (especially [*pipermail/tahoe-dev/2010-April/004237.html this message by Brian Warner])
Literal caps are supported for immutable files and immutable directories (see [the Capabilities wiki page](Capabilities)). Whenever the contents of the file or directory are small enough that it would be more efficient to fit the contents into the cap itself than the store the contents remotely and use the cap to fetch it, then it becomes a literal cap.
**<a name="Q23_FUSE">Q23:</a> Can I access files stored in Tahoe-LAFS via FUSE?**
A:
Yes. Tahoe-LAFS comes with an [SFTP server]source:docs/frontends/FTP-and-SFTP.rst. If you point [sshfs](http://fuse.sourceforge.net/sshfs.html) at the SFTP server then you have access to Tahoe-LAFS through FUSE. Alternately, [pyfilesystem](https://code.google.com/p/pyfilesystem/) interfaces directly with Tahoe-LAFS through the latter's [WAPI]source:docs/frontends/webapi.rst and provides both FUSE and Microsoft Windows filesystem access. See #1353 for discussion of possible improvements to FUSE integration. See [Zooko's post to freedombox-discuss](http://lists.alioth.debian.org/pipermail/freedombox-discuss/2011-November/003162.html) and [Zooko's post to Google+](https://plus.google.com/108313527900507320366/posts/ZrgdgLhV3NG) for Zooko's ramblings about the advisability of using FUSE for distributed filesystems in general and Tahoe-LAFS in particular.