I am really happy that my MacFuse+Macfusion is working again. While the command line and version control are (most of the time) my friends, sometimes a client doesn’t use a VCS and I am forced to work directly on the server. MacFuse lets you mount these file systems over SSH like any other Mac volume. This makes it easy to work on the whole codebase at once on the mount point, vs. the download-upload FTP client method. Using the finder to browse around the server also makes it far easier to locate assets like image files.
This post builds on the the already well documented concepts outlined in this blog post to provide additional details for a Snow Leopard, and handle some additional configurations for the 64-bit kernel. The previous post explains in detail how these technologies work, and provides screen shots to guide you in your configurations.
MacFUSE
The latest version of MacFUSE on the google code page is not compatible with the 64bit kernel. You need to download the 2.1.9 beta from this link.
SSHFS
Download the sshfs-static-leopard.gz from this wiki post and replace the sshfs-static executable in the MacFusion.app package.
To use sshfs from the command line, symlink the new binary to a location in your path, i.e.:
sudo ln -s /Applications/Macfusion.app/Contents/PlugIns/sshfs.mfplugin/Contents/Resources/sshfs-static /usr/local/bin/sshfs
If MacFusion still refuses to complete a connection to a remote server, quit MacFusion, open up a terminal and:
$ cd /Applications/Macfusion.app/Contents/PlugIns/sshfs.mfplugin/Contents/Resources/
$ mv sshnodelay.so sshnodelay.so.bak
source: http://rackerhacker.com/2009/08/28/fix-macfusion-on-snow-leopard/
LINKS
- How to manually compile svn checkout of MacFUES for the 64 bit kernel: http://www.5dollarwhitebox.org/drupal/node/97
- How to prevent .DS_Store file creation over network connections: http://support.apple.com/kb/HT1629
find me on
