2008/10/28 Amit Singh <[EMAIL PROTECTED]>: > > On Oct 27, 8:01 pm, "Rhythmic Fistman" <[EMAIL PROTECTED]> wrote: >> Yours, >> Confused. > > Let me try to be clear(er). > > xattrs though ._ files do work in a properly-written MacFUSE file > system on Tiger.
You're right. However it depends on how you define "works", as the interaction here with cp/copyfile is not obvious, so I'd hazard that even "properly-written" MacFUSE filesystems could fall foul of the problem I had: My fuse filesystem is read only, which I was faithfully reporting in getattr. cp copies the data fork by hand and then the extended attributes via copyfile. It seems that on Tiger the destination file becomes read only before the extended attributes are written, so the fsetxattr call fails. I'm not sure but I think the fault lies with the Tiger implementation of copyfile. The work around is to incorrectly report my files as being read/write. This also disposes of the annoyance of having read only files lying about the place. The files of course aren't writable, and writable opens fail, but the consequences don't seem to be that bad. For me the conclusion is: On Tiger getattr should return 666 for all readable files This makes xattrs work with cp. Of course if you want Finder/FileManager compatibility you have to use appledouble files, but even then the golden rule remains that for cp compatibility on Tiger you must pretend that your files are writable. Thanks for the loopback suggestion, I'll try that soon. Cheers, RF. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MacFUSE" 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?hl=en -~----------~----~----~----~------~----~------~--~---
