From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <cygwin-return-54265-listarch-cygwin=sourceware.cygnus.com@cygwin.com>
Received: (qmail 14768 invoked by alias); 17 Jul 2002 03:36:20 -0000
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Received: (qmail 14761 invoked from network); 17 Jul 2002 03:36:18 -0000
Received: from unknown (HELO lacrosse.corp.redhat.com) (66.187.233.200)
  by sources.redhat.com with SMTP; 17 Jul 2002 03:36:18 -0000
Received: from redhat.com (vpn50-41.rdu.redhat.com [172.16.50.41])
	by lacrosse.corp.redhat.com (8.11.6/8.9.3) with ESMTP id g6H3aFs08315
	for <cygwin@cygwin.com>; Tue, 16 Jul 2002 23:36:15 -0400
Received: by redhat.com (Postfix, from userid 201)
	id A65D91C359; Tue, 16 Jul 2002 23:36:31 -0400 (EDT)
Date: Wed, 17 Jul 2002 00:58:00 -0000
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: gzip.exe as symlink breaks NTEmacs's jka-compr.el
Message-ID: <20020717033631.GA25069@redhat.com>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <rrschulz@cris.com> <5.1.0.14.2.20020716182754.02f3df30@pop3.cris.com> <5.1.0.14.2.20020716185624.03113ce8@pop3.cris.com> <5.1.0.14.2.20020716193950.03031af8@pop3.cris.com> <006701c22d3f$d6b486e0$d500a8c0@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
X-SW-Source: 2002-07/txt/msg01329.txt.bz2

>> 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/