Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <006701c22d3f$d6b486e0$d500a8c0@study2> From: "Robert Collins" To: , "Randall R Schulz" References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020716182754 DOT 02f3df30 AT pop3 DOT cris DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020716185624 DOT 03113ce8 AT pop3 DOT cris DOT com> <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020716193950 DOT 03031af8 AT pop3 DOT cris DOT com> Subject: Re: gzip.exe as symlink breaks NTEmacs's jka-compr.el Date: Wed, 17 Jul 2002 13:12:52 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 ----- Original Message ----- From: "Randall R Schulz" To: "Robert Collins" ; > >It's not the ln smarts that are needed, its the cygwin1.dll hard link > >smarts. I'd happily accept a patch to the cygfile:// handler in setup to > >perform hard links rather thank copies. Of course, the package maintainers > >will suddenly all need to build on NTFS as well, and with hardlinks to boot, > >before anything changes. > > It occurred to me that Cygwin1.dll might be making the copy on FAT file > systems, but that didn't seem to make much sense, since the "hard link > fails on FAT" case seems awfully close to the "cross-dev link fails" case > that a conventional Unix "ln" already has to deal with. Huh? Cygwin1.dll doesn't make a copy on FAT - it fails as you have just noted.. Setup.exe's cygfile:// handler makes copies. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/