Dear list! Using a MacFuse Filesystem implementation that does not implement any of the methods concerning extended attributes (or even uses auto_xattrs), MacFuse creates ._files containing those attributes. While those files seem to work correctly when MacFuse accesses them, they are not usable elsewhere.
For instance: Running LoopBackFS I copy a textclipping file to the mounted FS. If I doubleclick it on the FS volume, the clipping is still ok. However, if I navigate to the /tmp directory where LoopBackFS has actually created a textclipping file and a ._textclipping file (which the Finder would usually combine automatically), the textclipping cannot be opened anymore. (it is empty as it would be if the appledouble file would be missing). Comparing a MacFUSE created ._file with a version that is created by "SplitForks" shows that both files are significantly different. Was it wrong to assume that the "._file" created by MacFUSE is a standard appledouble file that would work copied on any filesystem that does not support extended attributes or is this a bug? Regards Thomas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" group. To post to this group, send email to macfuse-devel@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
