Sorry to all for my initial double post - accidental. Thanks for the suggestion of comparison with LoopBack. I'll try that, particularly in comparing getattr calls
I did go ahead with implementing the xattr calls and that came close to solving the drag-n-drop problem with Finder, but not quite. Finder calls setxattr(path, "com.apple.FinderInfo", value, 32, ...) to save 32 bytes on the dropped file and calls getxattr(path, "com.apple.FinderInfo", value, 32, 0) to read them back ok. But, it also calls getxattr(path, "com.apple.ResourceFork", value, 0, 0) on the file. Tthat xattr doesn't exist and the -ENOATTR return value seems to trigger a bunch of getattr calls and eventual unlink. I do like that implementing the xattr calls seems to have eliminated its creation of apple double files. I don't think this is a MacFUSE problem but was just hoping for some insight into Finder's operation from folks who know better than me. The LoopBack tip might help me ferret it out. -- 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=.
