Hi all, Thanks for creating MacFUSE! I was overjoyed to find that porting my existing FUSE-based file system to the Mac was basically just a matter of recompiling.
I've released a commercial product, Cascade, that makes use of MacFUSE (and FUSE): http://www.conifersystems.com/cascade/ One of its components, Cascade File System, lets you view and edit Subversion and Perforce repositories without needing to "check out" a local copy of the repository files on your hard drive, so setting up a tree is an O(1) operation regardless of the size of the repository. Having worked on projects where I needed many gigabytes of files from the repository, well -- I wish I had this product back then. :) In addition, the results of automated builds/tests on your repository are exposed through the file system, too, so when you set up a tree it can effectively come "prebuilt". You can see a walkthrough of how this all works in the Flash demo on my web site. I've already reported a few issues with FUSE proper to the FUSE mailing list, and I won't repeat them here (I assume hope MacFUSE is closely tracking FUSE development?), but I did run into some issues specific to MacFUSE. The first issue is that the libfuse.dylib universal binary only contains 32-bit binaries. My file system benefits from a 64-bit address space and it would be wonderful if the next release could include an x86_64 build of libfuse.dylib. The other big issue has to do with how to get MacFUSE to mount a file system automatically at boot time. I can manually mount my file system with a command such as: sudo cfs_fuse /mnt/cfs -o [options] ...but I haven't really been able to figure out a solid way to get it to mount out of /etc/fstab with "sudo mount /mnt/cfs" or, better yet, mount automatically at boot time and show up as a directory under /Volumes without so much as needing to "mkdir" the directory. With some pretty severe hacking (adding a script /sbin/mount_fuse that did command line munging) I was able to get an explicit "sudo mount /mnt/cfs" to work, but even then, it wouldn't auto-mount at boot time. Wasn't quite sure, but seemed that it may have been a permissions problem. Anyway, the goal is to make it as user-friendly as possible, and I wasn't able to come up with a way to make that happen... I saw some mailing list traffic previously on this topic, and it didn't seem like anyone had any solid answers on how to get the file system to automount. -- Matt Craighead Founder/CEO, Conifer Systems LLC http://www.conifersystems.com 512-772-1834 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/macfuse?hl=en -~----------~----~----~----~------~----~------~--~---
