X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.8 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW
X-Spam-Check-By:	sourceware.org
In-Reply-To:	<4B97684F.7000703@towo.net>
References:	<CC11356C-47B3-4FD0-9A58-89A9691A52D8 AT von-campe DOT com> <20100304094847 DOT GZ17293 AT calimero DOT vinschen DOT de> <D85D47A6-32FD-4FFE-A99C-D7FD055E8F67 AT von-campe DOT com> <20100304114902 DOT GC7980 AT calimero DOT vinschen DOT de> <E181D856-56A1-4AD5-BD5A-758A0D11EB79 AT von-campe DOT com> <4B9696F3 DOT 70004 AT cygwin DOT com> <4A05CDB7-413E-4920-989F-E9470BCBE658 AT von-campe DOT com> <4B97684F DOT 7000703 AT towo DOT net>
Mime-Version:	1.0 (Apple Message framework v753.1)
Message-Id:	<FF8F07FB-C8BA-452F-8DB8-DE0C3E569D19@von-campe.com>
Cc:	cygwin AT cygwin DOT com
From:	Alfred von Campe <alfred AT von-campe DOT com>
Subject:	Re: Strange symlink behaviour
Date:	Wed, 10 Mar 2010 07:59:55 -0500
To:	Thomas Wolff <towo AT towo DOT net>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Mar 10, 2010, at 4:37, Thomas Wolff wrote:

> Actually, if the file system does not support hard links, a tar  
> file that contains them doesn't properly extract at all, it will  
> rather report errors for those files.
> (At least that's what it does on a network filesystem whose mount  
> doesn't support hard links either.)
> So it's a problem to use hard links in tar for general use.

That's good to know.  In my limited experiments on the NAS box we use  
(which speaks both CIFS and NFS), extracting a tar file containing  
hard links from Windows via the Cygwin tar, appears to "do the right  
thing".  It even appears that it's an actual hard link when viewed  
from NFS (both files have the same inode).

Alfred


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

- Raw text -