Re: Standard OS X Compression format
Re: Standard OS X Compression format
- Subject: Re: Standard OS X Compression format
- From: Markus Hitter <email@hidden>
- Date: Tue, 20 Nov 2001 18:58:48 +0100
Am Dienstag den, 20. November 2001, um 13:54, schrieb Marcel Weiher:
._foo is treated specially only by (a) Carbon ...
... as Carbon is the only API (still) using Resource forks. For
Cocoa and Finder Info I'm not too sure where to draw the border.
... when (b) accessing files on a non-forked file system.
which currently is every filesystem supported by Darwin / OS X,
except HFS(+).
._foo is not special at all to Darwin!
Because Darwin doesn't make any use of resource forks. Does it?
On the Darwin 1.3.1 Install disk I couldn't find a single file
with a resource fork size > 0.
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?
You guess it: I were too lazy to figure out wether to bug
gnutar, hfstar or IRIX. My conclusion was: hfstar is pretty
useless for all non-HFS file systems, anyway. At least all the
additions to hfstar over gnutar.
On HFS+, it works great.
Error messages that report errors: trying to unpack resource
forks and finder info on a filesystem that does not support
these features...
You might consider not to include empty resource forks and
non-default finder info. The last time I had a look at hfstar
was about half a year ago, so please excuse if you improved this
already.
Please don't get me wrong after all this discussion: I
appreciate the very existence of hfstar (like hfspax) very much
since it jumps in where Apple left some sort of hole.
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/