Of course there's no extended attribute in Mac OS X for the creation date.
The reason MacFUSE doesn't support the creation date has nothing to do with Tiger compatibility. It has to do with the fact that MacFUSE is compatible with the cross-platform FUSE API. I have thought about extending the MacFUSE API, perhaps such that file systems can optionally use the extended API if they choose to be NOT cross platform. However, these are all "thoughts" so far--I have no timeframe for such extensions yet. Amit On Mar 21, 6:18 pm, Guy Brooker <[EMAIL PROTECTED]> wrote: > Thanks ted, > > that is very helpful. I have been digging into the creation date > story, and still haven't figured out how it is stored; it seems to be > deep in HFS+. In the Carbon API FSSetCatalogInfo() allows five > different dates to be set for a given file, however the posix API only > seems to have three dates associated (missing the creation and backup > dates). > > If you set a creation date using /Developer/Tools/SetFile -d there > does not seem to be any extended attributes or resources added to the > file, and you can delete the folders .DS_Store file, without losing > the creation date. > > The only hope is the new stat64 calls added to the Leopard posix API, > which add a field for the file "birth time" to the stat structure. I > guess as MacFuse is still backwards compatible with Tiger, it won't be > supporting those calls for a while. > > So looks like I'm going to have to give up on creation date for now, > unless anyone has any further suggestions. > > Cheers, > Guy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "macfuse-devel" 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-devel?hl=en -~----------~----~----~----~------~----~------~--~---
