whether MacFUSE works on Snow Leopard probably depends on the kernel bitness (https://trac.macports.org/ticket/30129)

[Imported from Trac: page SftpFrontend, version 70]
davidsarah 2011-08-21 22:20:03 +00:00
parent b7d8b12d29
commit 38898469b8

@ -77,7 +77,7 @@ For Mac OS X, a patched version of sshfs is included as part of [MacFUSE](http:/
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 Bryan Pahm, OSXFUSE, and FUSE4X forks have not been tested.
Version 2.0.3 *does* work on Leopard (Mac OS X 10.5.8). It has not been tested with Snow Leopard. All of the caveats noted for Linux above apply, and the following additional ones:
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:
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`.