Hi! Thanks for your quick replies. I can confirm that using the new LoopBack example and the new MacFUSE version now fixes the issue - when xattrs are supported in the implementing fs.
However - If xattr implementation methods are removed (and AppleDouble files should be created), the created AppleDouble file is still damaged and of size 128kb. Unfortunately for me I need to solve it in that way because I need the AppleDouble files. What I have learned from your comments to my questions in another thread, if the fs does not implement xattrs, the kernel itself initiates the creation of AppleDouble files. In my understanding this would mean that the kernel subsequently calles the filesystems open, write and probably read etc. for the AppleDouble file. If MacFUSE does not interfere here I do not understand why the position attribute would have an influence for that case. (wouldn´t the Finder just create and read AppleDouble filechunks?) Does this mean that I still have no chance getting this to work on the implementation side if I need to use AppleDouble files? Thanks for your time, 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 -~----------~----~----~----~------~----~------~--~---