Re: Metadata support
Re: Metadata support
- Subject: Re: Metadata support
- From: "Jordan K. Hubbard" <email@hidden>
- Date: Sun, 25 Jun 2006 23:52:31 -0700
On Jun 25, 2006, at 8:33 PM, Boyd Waters wrote:
On Jun 25, 2006, at 7:02 PM, Jordan K. Hubbard wrote:
What are you folks actually trying to do? Have you considered
that it might be the wrong thing? :)
Oh, I consider that I'm doing the wrong thing about six times
before breakfast... :)
I'm trying to back up my files from Mac OSX to Linux or FreeBSD,
and I want the extended attributes to be mapped to the foreign file
system so that a file's attributes may travel reliably from copy to
copy on the Linux side (e.g., across server backups) and still make
sense when the file is examined by a Mac.
Ah, but they are. That's why you want the ._ files to be used on the
Linux side - so Linux will not attempt to interpret the EAs or
(worse) the ACLs. Sure, one could theoretically map it all across if
the Linux filesystem supported EAs and ACLs and you had a very clear
knowledge of the MacOSX ACL semantics vs the Linux ones and could
translate everything (in both directions) with full fidelity, but
gah! All you need is one area where the semantics are disjoint (max
EA length, EA naming rules, fundamental ACL incompatibility, etc) to
bring down the whole house of cards. If you tar up a MacOSX volume
(or rsync from one) and extract the bits on a FreeBSD or a Linux
system, you'll get the ._ files on the far end and can later send
those back with all the right behavior on the MacOSX side. Unless
your Linux backup scripts are choosing to throw ._ files away or
something, I don't see the problem.
But Finder attributes, to name another application, are _not_
derived from the underlying data: where it a file's Finder label
stored? In some other file. Surprise, surprise...
Unless you're doing full-volume backups, I think it's folly to try
and preserve the association of Finder attributes with their files
(see previous message to Mr. Shoup).
I want per-file attributes to be maintained with the file -
semantically "in" the file.
And they are. It's only when you export/archive them that you see
the ._ files, for all the good reasons I outlined above.
- Jordan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden