On Oct 31, 2007, at 7:45 PM, Ron Aldrich wrote:
> Then, when Finder goes to create an icon for the volume, it fails > because the mount point doesn't exist yet. > I fixed this problem by writing a small, generic wrapper for FUSE filesystems. MacFUSE, in Tiger, posted a handful of distributed notifications so you could wait until a volume had successfully mounted before returning control to, say, DiskArbitration. By waiting for those notifications, DiskArbitration and its clients blocked until the filesystem was ready, and then returned. Thus, no DiskArbitration notifications were delivered before the filesystem was ready. The problem you're seeing stems from the fact that FUSE volumes daemonize from the command line, so the invoked command returns success before the filesystem is fully mounted by the background daemon. The notifications, I believe, are documented in the MacFUSE wiki. I don't have the time immediately, but I can get back to you later with my fuse_wait wrapper. If you want to throw together your own, that's fine; it shouldn't take but an hour, if that. As for the unmount problem, I can't think of anything right now. - Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
