site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com User-agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 On 27/06/06 21:17, Dan Shoop wrote: [...] # note changed symlink ownership ooblek:~ dshoop$ ls -alseo xyzzy2 [...] # note changed xattr structure and missing xattr on filexattr ooblek:~ dshoop$ xattr --list xyzzy2/* xyzzy2/file xyzzy2/fileacl com.apple.acl.text !#acl 1 group:ABCDEFAB-CDEF-ABCD-EFAB-CDEF00000050:admin:80:allow:read xyzzy2/filebsdflags xyzzy2/filesymlink xyzzy2/filexattr But this one is rather amusing (?), and makes me remind of: <http://lists.apple.com/archives/macos-x-server/2006/Apr/msg00568.html> Axel _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... # extract tarball ooblek:~ dshoop$ mkdir xyzzy2 ooblek:~ dshoop$ /usr/bin/tar -xv --preserve --atime-preserve -f xyzzy.tar -C xyzzy2/ [...] Well... the symlink ownership seems to be preserved here if one extracts as user root. ;-) It really looks like that all these tools (tar, rsync...) encounter similar problems, very likely because of copyfile() and/or the libraries it relies upon. For example, could you create a tarball of xyzzy2, and then extract it to xyzzy3? It tried here, by reproducing your experiments, and just got a crash very similar to the one described in point [G] of my April's post (note that I updated to 10.4.7 today). This email sent to site_archiver@lists.apple.com