ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2024-12-19 21:17:54 +00:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
The Tahoe-LAFS decentralized secure filesystem.
2,998 Commits 185 Branches 90 Tags 89 MiB
Python 98.1%
HTML 0.9%
Nix 0.3%
Shell 0.3%
Makefile 0.2%
Other 0.1%
6763df16f1
Go to file
robk-tahoe 6763df16f1 fuse/impl_c: UNDO --auto-fsid option 
rolling back:

Thu Sep 25 14:42:23 BST 2008  robk-tahoe@allmydata.com
  * fuse/impl_c: add --auto-fsid option
  
  this was inspired by reading the fuse docs and discovering the 'fsid' option
  to fuse_main, and was _intended_ to support a sort of 'stability' to the 
  filesystem (specifically derived from the root-uri mounted, whether directly
  or via an alias) to support mac aliases across unmount/remount etc.
  
  some experimentation shows that that doesn't actually work, and that, at
  least for mac aliases in my testing, they're tied to path-to-mountpoint and
  not to the fsid - which seems to have no bearing.  perhaps the 'local' flag
  is causing weirdness therein.
  
  at any rate, I'm recording it simply for posterity, in case it turns out to
  be useful after all somewhere down the road.
  

    M ./contrib/fuse/impl_c/blackmatch.py +13
2008-09-25 06:47:30 -07:00
bin bin/tahoe: reflow error messages 2008-09-11 18:02:25 -07:00
contrib fuse/impl_c: UNDO --auto-fsid option 2008-09-25 06:47:30 -07:00
docs CLI: reconcile webopen changes 2008-09-24 08:20:02 -07:00
mac fuse/impl_c: move mac tahoefuse impl out into contrib/fuse 2008-09-24 18:42:14 -07:00
misc misc/make-canary-files.py: tool to create 'canary files', explained in the docstring 2008-09-24 17:47:16 -07:00
src/allmydata manhole: be more tolerant of authorized_keys. files in .tahoe 2008-09-24 20:11:49 -07:00
twisted/plugins change #!/usr/bin/python to #!/usr/bin/env python 2007-03-29 14:01:28 -07:00
windows windows/Makefile: fix dependencies: windows-installer must cause windows-exe to run 2008-09-11 22:21:51 -07:00
_auto_deps.py use foolscap's new app_versions API, require foolscap-0.3.1 2008-09-20 11:38:53 -07:00
.darcs-boringfile .darcs-boringfile ignore tahoe-deps and tahoe-deps.tar.gz 2008-09-17 12:59:38 -07:00
COPYING.GPL new licences, move details from README to doc/install-details.html 2008-01-04 12:27:42 -07:00
COPYING.TGPPL.html more introductory doc cleanup 2008-01-04 18:09:19 -07:00
CREDITS CREDITS: thanks to Chris Galvan 2008-08-27 11:39:50 -07:00
ez_setup.py setup: require setuptools >= v0.6c8 2008-03-26 12:13:02 -07:00
Makefile fuse/impl_c: move mac tahoefuse impl out into contrib/fuse 2008-09-24 18:42:14 -07:00
NEWS NEWS: finish editing for the upcoming 1.3.0 release 2008-09-19 12:30:53 -07:00
README setup: update README to point to known_issues.txt 2008-07-21 18:02:29 -07:00
relnotes.txt relnotes.txt: update and edit for the 1.2.0 release! 2008-07-21 18:04:03 -07:00
setup.cfg Makefile,docs: tahoe-deps.tar.gz now lives in separate source/deps/ directory on http://allmydata.org 2008-09-17 13:44:52 -07:00
setup.py setup: fix site-dirs to find system installed twisted on mac. 2008-09-24 10:42:55 -07:00
Tahoe.home rename bin/allmydata-tahoe to bin/tahoe. Closes #155. 2007-10-11 03:38:24 -07:00

README 

Welcome to the Tahoe project [1], a secure, decentralized,
fault-tolerant filesystem.  All of the source code is available under
a Free Software, Open Source licence (or two).

Please see docs/about.html for an introduction, docs/install.html for
install instructions, docs/running.html for usage instructions.

Finally, see docs/known_issues.txt for things that you need to know
about if you are relying on Tahoe to store your valuable data.

[1] http://allmydata.org