Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-Id: <5.1.0.14.2.20020716193950.03031af8@pop3.cris.com>
X-Sender: rrschulz AT pop3 DOT cris DOT com
Date: Tue, 16 Jul 2002 19:53:19 -0700
To: "Robert Collins" <robert DOT collins AT syncretize DOT net>, cygwin AT cygwin DOT com
From: Randall R Schulz <rrschulz AT cris DOT com>
Subject: Re: gzip.exe as symlink breaks NTEmacs's jka-compr.el
In-Reply-To: <003d01c22d3a$5e23e900$d500a8c0@study2>
References: <Message from Randall R Schulz <rrschulz AT cris DOT com>
 <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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed

Rob,

At 19:33 2002-07-16, you wrote:

>----- Original Message -----
>From: "Randall R Schulz" <rrschulz AT cris DOT com>
>To: "Jon Cast" <jcast AT ou DOT edu>
>
> > I know that if one just uses the "ln" command (no "-s" option) on a FAT
> > volume you get a copy. If Cygwin packages used hard links for program
> > aliases (does the TAR format support hard links?) and Setup.exe was given
> > the same smarts as the "ln" command, you'd get space-wasting copies on FAT
> > volumes and fast, space-efficient hard links on NTFS.
>
>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.

"Real Users Use NTFS" (sm)


>Rob


Randall Schulz
Mountain View, CA USA


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