• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Resource Fork as Extended Attributes
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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+ ?.

No, although you can access them via the API.

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

References: 
 >Resource Fork as Extended Attributes (From: shailesh jain <email@hidden>)
 >Re: Resource Fork as Extended Attributes (From: Chris Suter <email@hidden>)

  • Prev by Date: Re: Resource Fork as Extended Attributes
  • Next by Date: Re: Resource Fork as Extended Attributes
  • Previous by thread: Re: Resource Fork as Extended Attributes
  • Next by thread: Re: Resource Fork as Extended Attributes
  • Index(es):
    • Date
    • Thread