Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: "Jonadab the Unsightly One" Organization: There is no organisation. To: cygwin AT cygwin DOT com Date: Sat, 26 May 2001 23:31:52 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: RE: Serious brokeness of treating .lnk files as symlinks Reply-to: jonadab AT bright DOT net Message-ID: <3B103CE8.4532.6BCFED@localhost> In-reply-to: <000401c0e5bf$3eefa1a0$21c9ca95@mow.siemens.ru> X-Eric-Conspiracy: My name is not Eric. X-Platform: Windows '95 OSR2 (heavily adjusted and customised) X-mailer: Pegasus Mail for Win32 (v3.12) Andrej Borsenkow regarding RE: Serious brokeness of treating .lnk files as s: [tar does not treat .lnk files as such] # I am afraid there is no solution without breaking compatibility. On Unix # symlink does not have any "contents" except the file name it points to. So, # tar saves just this filename. This allows tar archive to be moved to any # other compliant system. If you tar your files on Cygwin and restore them on # Unix you get identical filesystem structure including symlinks. If the problem is with the tar format, then you can solve it by using some other archival system -- for example, pkzip -- for moving files from one Windows system to another or within one Windows system. What tar does is IIUC right for moving files to a Unix system. Is there a way to get tar to treat .lnk files as regular files (rather than as symlinks) with a commandline option? That would also solve the problem, I think. -- jonadab -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple