As a side note, Leopard introduced a new API called "copyfile" (man
copyfile) that is designed to handle fork and EA copying better which
is why you're seeing Leopard Finder behave better than Tiger Finder.

Sam


On Tue, Oct 28, 2008 at 7:47 AM, Sam Moffatt <[EMAIL PROTECTED]> wrote:
> I didn't do any investigation into resource forks but I wrote a C
> based FS that supported metadata just dandy. Ensure you're using cp
> --preserve=all otherwise it will ignore any extended attributes in the
> copy, but I was on Tiger and this did function correctly with EA's
> being copied appropriately. I can't retest again since everything I've
> got has upgraded to Leopard.
>
> Sam
>
>
> On Tue, Oct 28, 2008 at 3:26 AM, RF <[EMAIL PROTECTED]> wrote:
>>
>> I'm having trouble getting resource forks in fuse filesystems working
>> on
>> both Tiger and Leopard. I'm using versions 1.7.0/1.7.1.
>>
>> By "working" I mean copying correctly from my fs with both "cp" and
>> the Finder.
>>
>> On Leopard everything is very simple as xattrs work everywhere.
>>
>> On Tiger things are more difficult. The Finder completely ignores
>> extended attributes.
>> and cp reads extended attributes, but seems to discard the result.
>>
>> So I added an appledouble interface for Tiger. After much trial and
>> error I got
>> it working with the Tiger Finder (very fussy, e.g. finder info is
>> compulsory,
>> magic #0x51607, version 0x20000), however for cp copying, the result
>> is
>> basically the same as with xattrs: cp reads and discards my
>> appledouble file.
>>
>> Observations:
>>  Tiger cp works for apple double files on other FSs (e.g. fat32 usb
>> key)
>>
>>  On Leopard cp via appledouble only works if you enable auto_xattr
>> (breaks vol icon)
>>
>>  At some point in the recent past, volume icons stopped working for
>> me on Tiger
>>
>>  I'm synthesizing my own appledouble files. Finder info is 32 zeroes.
>>
>>
>> Can anyone offer any insight?
>>
>> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to