Hard links in tar, not untaring as expected

Eric Blake ebb9@byu.net
Tue Jan 23 03:29:00 GMT 2007

Hash: SHA1

According to Sally, Gene on 1/22/2007 11:50 AM:
> drwxr-xr-x UserName GroupName 0 2007-01-18 16:35:22 test/
> -rw-r--r-- UserName GroupName 9 2007-01-18 16:35:22 test/hardlink
> -rw-r--r-- UserName GroupName 0 2007-01-18 16:35:22 test/orig-file link
> to test/hardlink
> Obviously, there's something different, but I can't figure out what that
> is.  Is anyone aware of some subtle changes in the win API that could
> cause this problem?  Maybe there some permission settings that could
> cause this problem? 

Could it be that one of your systems uses a FAT32 drive, which does not
support hard links?  I couldn't reproduce your failure.

But speaking of hard links and tar, I find it annoying that setup.exe
won't even try to create hard links when a tar file requests them.  A good
example of this is the git- package - it contains 55 hard
links to usr/bin/git.exe, but setup.exe unpacks it into 55 separate files,
rather than a single file, thus occupying 26 megabytes more hard drive
space than strictly necessary on NTFS.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@byu.net
volunteer cygwin tar maintainer
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

More information about the Cygwin mailing list