The next release of MacFUSE (at least for Leopard, and perhaps for Tiger as well) will let you alter the behavior of fuse_is_shortcircuit_xattr() through a mount-time argument. So, something like "-o noautoextattr" will cause _all_ extended attribute requests to go up to user space. Therefore, feel free to experiment and if something works for you, I'd be interested to hear about it.
Amit On Aug 11, 5:34 am, "Hamish Allan" <[EMAIL PROTECTED]> wrote: > On 8/10/07, Amit Singh <[EMAIL PROTECTED]> wrote: > > > BTW, core/10.x/fusefs/fuse_internal.h has > > fuse_is_shortcircuit_xattr(), which decides if "com.apple.FinderInfo" > > and "com.apple.ResourceFork" should be forwarded to user-space at all. > > In the current releases, they are handled in the kernel by default > > (through ._ files). If you want these to go up to user space in the > > first place, comment out the corresponding bcmp()'s in the > > aforementioned function. Not to say that will make Finder & Co. happy > > under all circumstances. > > I'd be wary of making a filesystem that would require anything other > than the vanilla MacFUSE release! > > Also from a cursory examination of calls to > fuse_is_shortcircuit_xattr(), it's only called from > getxattr/setxattr/removexattr and not listxattr, so I'm pretty sure it > would make no difference to my Finder issue. > > Thanks, > Hamish --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
