Changes between Version 75 and Version 76 of SftpFrontend

Timestamp:

2012-01-24T10:48:02Z (13 years ago)

Author:

lebek

Comment:

detail Fuse4X status, demote MacFUSE to "legacy support" option

SftpFrontend

@@ -77 +77 @@
 == sshfs on Mac OS X ==
 
-For Mac OS X, a patched version of sshfs is included as part of [http://code.google.com/p/macfuse/ MacFUSE].
+There are currently three major forks of the deceased MacFUSE: [http://fuse4x.org/ Fuse4X], [http://osxfuse.github.com/ OSXFUSE], and [https://github.com/tuxera/macfuse Tuxera]. Fuse4X has the advantage of compatibility with the [http://fuse.sourceforge.net/ upstream FUSE project], meaning that existing FUSE filesystems (such as sshfs) do not require patching in order to work. Fuse4X ([https://github.com/downloads/fuse4x/fuse4x/Fuse4X-0.8.14.pkg v0.8.14]) along with sshfs ([https://github.com/fuse4x/sshfs/zipball/master v2.3.0]) have been tested and confirmed to work on Lion (Mac OS X 10.7) - results for older versions of OS X would be appreciated.
 
-However, development of MacFUSE stalled at version 2.0.3, which does not work on the 64-bit kernel used by default in Lion, and it has subsequently [http://www.mail-archive.com/macfuse@googlegroups.com/msg02517.html splintered into several forks]. The Tuxera fork (version 2.2.1) does not work with Tahoe-LAFS, possibly due to issue (2) in [http://osdir.com/ml/macfuse/2011-08/msg00052.html this post]. The [https://github.com/osxfuse/osxfuse OSXFUSE], and [http://fuse4x.org/ FUSE4X] forks have not been tested. If you want to test this, we recommend starting with FUSE4X.
+The Tuxera fork (v2.2.1) does not work with Tahoe-LAFS, possibly due to issue (2) in [http://osdir.com/ml/macfuse/2011-08/msg00052.html this post]. OSXFUSE has not been tested.
 
-Version 2.0.3 ''does'' work on Leopard (Mac OS X 10.5.8). On Snow Leopard it will probably work only if you are using a 32-bit kernel (but this has not been tested). All of the caveats noted for Linux above apply, and the following additional ones:
+If for legacy support reasons you wish to use MacFUSE - development of which stalled at version 2.0.3 - you will need to used 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).
 
-The MacFUSE version of sshfs stores "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}}}.
+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}}}.
 
 !TextEdit and vi are known to have problems editing files on a Tahoe-via-sshfs filesystem on Mac OS X.
-
 
 == Gnome virtual filesystem (gvfs) ==