From dd62f62660aac685ac09c17651ff279a2c8bb9f8 Mon Sep 17 00:00:00 2001 From: lebek <> Date: Tue, 24 Jan 2012 10:48:02 +0000 Subject: [PATCH] detail Fuse4X status, demote MacFUSE to "legacy support" option [Imported from Trac: page SftpFrontend, version 76] --- SftpFrontend.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/SftpFrontend.md b/SftpFrontend.md index c8cc196..5814af7 100644 --- a/SftpFrontend.md +++ b/SftpFrontend.md @@ -76,17 +76,18 @@ If you encounter problems, please use the debugging options `-o debug,sshfs_debu ## sshfs on Mac OS X -For Mac OS X, a patched version of sshfs is included as part of [MacFUSE](http://code.google.com/p/macfuse/). +There are currently three major forks of the deceased MacFUSE: [Fuse4X](http://fuse4x.org/), [OSXFUSE](http://osxfuse.github.com/), and [Tuxera](https://github.com/tuxera/macfuse). 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. -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 [splintered into several forks](@@http://www.mail-archive.com/macfuse@googlegroups.com/msg02517.html@@). The Tuxera fork (version 2.2.1) does not work with Tahoe-LAFS, possibly due to issue (2) in [this post](http://osdir.com/ml/macfuse/2011-08/msg00052.html). The [OSXFUSE](https://github.com/osxfuse/osxfuse), and [FUSE4X](http://fuse4x.org/) 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 [this post](http://osdir.com/ml/macfuse/2011-08/msg00052.html). 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) [gvfs](https://fedoraproject.org/wiki/Features/Gvfs) is a set of filesystem adapters provided with the Gnome window system. It can be used in two ways: either via the [GIO API](http://library.gnome.org/devel/gio/unstable/), or via a FUSE layer called gvfs-FUSE (not to be confused with sshfs).