Re: Resource Fork as Extended Attributes
Re: Resource Fork as Extended Attributes
- Subject: Re: Resource Fork as Extended Attributes
- From: shailesh jain <email@hidden>
- Date: Tue, 14 Jul 2009 21:00:01 -0700
On Tue, Jul 14, 2009 at 8:43 PM, Chris Suter
<email@hidden> wrote:
Hi Shail,
On Wed, Jul 15, 2009 at 12:46 PM, shailesh
jain<
email@hidden> wrote:
> Are resource forks and finder metadata stored as Extended attributes on OS
> X 10.4+ ?.
Cool. Will Lookup API's.
> Also, what is
> best way to handle resource forks and metadata, if the file is going to be
> transferred on different file systems (NTFS, ext3 etc) and back ?
I'm not sure. Ideally you'd use extent based extended attributes, but
I don't think that's widely supported yet (you have to enable them—I
forget exactly how you do that). Otherwise, you could look at storing
them within the resource fork but I believe that has size limits. I'm
afraid I don't know much about the Apple Double format but it's worth
looking into. If the streams are small, you can certainly use extended
attributes.
File store from NTFS -> HFS means that stream could be as big as file, thus
confining it to extended attributes would be impossible.
BTW: I think cross posting is generally frowned upon.
I think Apple's implementation of NFS and rsync fakes it using AppleDouble Format ?
Regards,
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden