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.
On Aug 8, 12:33 pm, "Hamish Allan" <[EMAIL PROTECTED]> wrote: > On 8/8/07, Amit Singh <[EMAIL PROTECTED]> wrote: > > > (they should)--even for things like "com.apple.FinderInfo". > > I'm surprised by this -- I thought all that transparency was handled > by the system call. > > Thanks for the tip, > 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 -~----------~----~----~----~------~----~------~--~---
