Re: Standard OS X Compression format
Re: Standard OS X Compression format
- Subject: Re: Standard OS X Compression format
- From: Marcel Weiher <email@hidden>
- Date: Tue, 20 Nov 2001 13:54:47 +0100
On Tuesday, November 20, 2001, at 01:10 PM, Markus Hitter wrote:
Am Samstag den, 17. November 2001, um 15:31, schrieb Marcel Weiher:
what if you have both a file named "foo" and one named "._foo" in your
current directory?
You're lost, then. All OS X Apps are lost as well. "._foo" is simply a
reserved name scheme (on Darwin / OS X).
This turns out not to be the case. ._foo is treated specially only by
(a) Carbon when (b) accessing files on a non-forked file system. ._foo
is not special at all to Darwin!
The big advantage of using this special file is: You can un-tar your
archive on a foreign OS as well, then mount this volume (e.g. NFS) on a
OS X box and everything will work fine.
Yes, I see the attraction of this, and I must admit I am attracted as
well. However, this is a translation of a native file-system format to
a simulation of that file-system format. While a nice feature, that is
the task of a different program.
You can even rearrange your files on a foreign OS without any data
loss, if you're careful. It's simply a lot more cross-platform
Using <data-file>/rsrc is safe because that is a path that can simply
not happen on a non-forked file-system.
Well, last time I tried, an archive packed with hfstar core dumped
gnutar on IRIX when trying to unpackage the thing.
Hmm, I can't find the bug-report that you surely must have sent...can
you resend?
Not to mention the big buch of error messages until it did.
Error messages that report errors: trying to unpack resource forks and
finder info on a filesystem that does not support these features...
Marcel
--
Marcel Weiher Metaobject Software Technologies
email@hidden www.metaobject.com
Metaprogramming for the Graphic Arts. HOM, IDEAs, MetaAd etc.