Very interesting stuff! Glad someone just took the ball and ran with it, so to speak.
I'm currently in mid-development of a filesystem which i'm building against the MacFUSE Obj-C API, so I guess my two questions are: 1. Should I switch to Fuse4X? (I'm guessing 'yes' ;) 2. How much work will that be? Is there still an Obj-C API? Is it the same? Regards Rory On 15 Jun 2011, at 19:14, Anatol Pomozov <[email protected]> wrote: > Hi > > On Wed, Jun 15, 2011 at 10:23 AM, Joe Auty <[email protected]> wrote: > Awesome! > > I take it that since sshfs is included here and it overrides the > /usr/local/bin/sshfs installed by MacFUSE that applications like Macfusion > will work under Fuse4X? > > As far as I know Macfusion uses its own copy of sshfs binary bundled into > macfusion distribution. So macfusion shouldn't be affected by Fuse4X. > > As for other tools that use /usr/local/bin/sshfs - they also should work the > same way as before. Fuse4X has the same option names as MacFUSE. The only > difference as I remember is that Fuse4X does not have "kill_on_umount" option. > -- > 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. -- 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.
