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 Date: Tue, 16 Jul 2002 23:36:31 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: gzip.exe as symlink breaks NTEmacs's jka-compr.el Message-ID: <20020717033631.GA25069@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com 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> <006701c22d3f$d6b486e0$d500a8c0 AT study2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <006701c22d3f$d6b486e0$d500a8c0@study2> User-Agent: Mutt/1.3.23.1i >> 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. Actually, the Cygwin link() function does make a copy on a FAT partition: extern "C" int _link (const char *a, const char *b) { . . . docopy: /* do this with a copy */ if (CopyFileA (real_a, real_b, 1)) res = 0; else __seterrno (); . . . cgf -- 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/