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

Update OS X section 

[Imported from Trac: page SftpFrontend, version 95]
daira 2017-02-05 12:24:06 +00:00
parent dbc3d2134a
commit 3a1fbcd423
1 changed files with 3 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
SftpFrontend.md

@ -72,17 +72,12 @@ If you encounter problems, please use the debugging options `-o debug,sshfs_debu
## sshfs on Mac OS X ## sshfs on Mac OS X
There are currently two major forks of the deceased MacFUSE: [Fuse4X](http://fuse4x.org/) and [OSXFUSE](http://osxfuse.github.com/). (There was also a [Tuxera](https://github.com/tuxera/macfuse) fork, but that is not maintained and did not work with Tahoe-LAFS.) In principle, sshfs should work with [OSXFUSE](http://osxfuse.github.com/) on Lion (Mac OS X 10.7) or later. However, this has not been tested for some time, at least since the merger with Fuse4X.
Experience reports of using sshfs with Tahoe on OS X would be appreciated.
Fuse4X has the advantage of compatibility with the [upstream FUSE project](http://fuse.sourceforge.net/), meaning that existing FUSE filesystems (such as sshfs) do not require patching in order to work. Fuse4X ([v0.8.14](https://github.com/downloads/fuse4x/fuse4x/Fuse4X-0.8.14.pkg)) along with sshfs ([v2.3.0](https://github.com/fuse4x/sshfs/zipball/master)) have been tested and confirmed to work on Lion (Mac OS X 10.7). Results for older versions of OS X would be appreciated.
OSXFUSE seems to work less well -- tarcieri on IRC reported: "last time I tried to use OSXFUSE with Tahoe+sshfs it just wigged out and crashed and unmounted the volume whenever I tried to read a file."
If for legacy support reasons you wish to use MacFUSE - development of which stalled at version 2.0.3 - you will need to use the patched sshfs included with the download. Version 2.0.3 *does* work on Leopard (Mac OS X 10.5.8). On Snow Leopard and Lion it might work if you use a 32-bit kernel (but this has not been tested).
All of the caveats noted for Linux above apply, and the following additional ones: All of the caveats noted for Linux above apply, and the following additional ones:
Fuse4X and MacFUSE store "extended attributes" in files with names starting with "`._`". For example the attributes for "`foo.txt`" would be stored in a file called "`._foo.txt`". Since some Mac OS X applications may depend on these attributes (especially for their own file formats), if you need to copy or move the original file then you should copy or move the attribute file along with it. The OS X `cp` and `mv` commands will do this by default; operations using the Tahoe WUI or CLI will not (unless you are moving all files in a directory). Note that filenames beginning with "`.`" are not listed by default by `ls`. OS X versions of FUSE store "extended attributes" in files with names starting with "`._`". For example the attributes for "`foo.txt`" would be stored in a file called "`._foo.txt`". Since some Mac OS X applications may depend on these attributes (especially for their own file formats), if you need to copy or move the original file then you should copy or move the attribute file along with it. The OS X `cp` and `mv` commands will do this by default; operations using the Tahoe WUI or CLI will not (unless you are moving all files in a directory). Note that filenames beginning with "`.`" are not listed by default by `ls`.
TextEdit and vi are known to have problems editing files on a Tahoe-via-sshfs filesystem on Mac OS X. TextEdit and vi are known to have problems editing files on a Tahoe-via-sshfs filesystem on Mac OS X.