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: <003d01c22d3a$5e23e900$d500a8c0@study2> From: "Robert Collins" To: "Jon Cast" , "Randall R Schulz" Cc: 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> Subject: Re: gzip.exe as symlink breaks NTEmacs's jka-compr.el Date: Wed, 17 Jul 2002 12:33:42 +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: "Jon Cast" > 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. 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/