Don't expect the plumbing needed to use extended attributes be there at all layers of the operating system. I assume you are expecting the Finder to automagically switch over to using extended attributes in this case. For comparison, write a simple program that calls setxattr/ listxattr etc. and see if your file system's xattr functions get called (they should)--even for things like "com.apple.FinderInfo".
Amit On Aug 7, 2:37 pm, "Hamish Allan" <[EMAIL PROTECTED]> wrote: > > > try to bind functions to .listxattr and .getxattr they are never > > > called. > > > When, and by whom are you expecting them to be called? Are you calling > > some xattr function(s) in a program of yours? > > Good point! I was expecting Finder, in the absence of an HFS+ > filesystem, to look for com.apple.FinderInfo and > com.apple.ResourceFork xattrs. After all, dot-underscore files are > only needed for filesystems which don't support xattrs, right? > > Okay, I know that those two particular extended attributes are > 'special', and are just really handles to different forks. But on a > foreign filesystem, if there's only a data fork (no AppleDouble file), > I'd have thought that xattrs should be the fallback. > > By the way, is Apple really serious about deprecating resource forks? > Icons contained in bundles are all well and good, but what's their > strategy for e.g., folders with custom icons such as are used > extensively in the Mac experience? > > 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 -~----------~----~----~----~------~----~------~--~---
