Re: Metadata support
Re: Metadata support
- Subject: Re: Metadata support
- From: Q <email@hidden>
- Date: Sun, 25 Jun 2006 18:02:30 +1000
- Delivered-to: email@hidden
- Delivered-to: email@hidden
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer; b=GBA5X6J7vKr0i4nCtNSelBdbglCxBrCiNKByEUBF/TQdLckpo6BaPeZhIu4hXEu16fX0lQEOcUE1bN5QkChm33PQFd5QsLrY105GuxoegdMezroxqb+EXAlt1dHrlKzT3K8bA8CJUb/Nidge6+p366CidAjNM+DGQmK8kR6R5IU=
On 25/06/2006, at 8:05 AM, Tomas Zahradnicky wrote:
Hello,
I've noticed that tar is able to store files' metadata and in order
to preserve it, it adds ._FILENAME file that appears to store
FileInfo and file's resource fork if there's one. Anyone knows if
this process is somewhere documented including the information it
stores beyond the raw resource fork?
Check out copyfile() included in the LibC library on tiger. The
source file copyfile.c (in the LibC source bundle from ADC) will tell
you everything you need to know about what's in those '._*' files.
My app uses libtar and when I extract everything, I need to
recombine ._files back into their owners. I have written something
that appears to work but would like to be sure I restored
everything I had to.
If you are making a tiger only app you can just use copyfile()
included in LibC, this is what the tiger unix tools like tar, cp,
rsync, etc use.
--
Seeya...Q
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
_____ / Quinton Dolan - email@hidden
__ __/ / / __/ / /
/ __ / _/ / / Gold Coast, QLD, Australia
__/ __/ __/ ____/ / - / Ph: +61 419 729 806
_______ /
_\
_______________________________________________
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