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: Thu, 12 Feb 2004 16:59:29 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: What kind of executable is zcat? Crashes from cmd.exe Message-ID: <20040212215929.GA19769@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com References: <6 DOT 0 DOT 1 DOT 1 DOT 0 DOT 20040212153628 DOT 0393dba8 AT 127 DOT 0 DOT 0 DOT 1> <001e01c3f1b1$b93d3ed0$6401a8c0 AT RossLap> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001e01c3f1b1$b93d3ed0$6401a8c0@RossLap> User-Agent: Mutt/1.4.1i X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com On Thu, Feb 12, 2004 at 03:46:44PM -0600, Ross Boulet wrote: >One other caveat I have found with using hard links (on an NTFS partition) >involves upgrades. I changed the symlink for ksh.exe -> pdksh.exe to a hard >link. When an new version of pdksh was installed, it resulted in two non >linked files. I had the new version as psksh.exe and the old version as >ksh.exe. Huh. I wonder why that happened. I would expect setup.exe to just overwrite one file, resulting in the change being reflected in the linked copy. I'm no longer familiar enough with setup's internals to say for sure if that is what happening but it does appear that the file is being deleted. That behavior could probably be changed with an appropriate PTC. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/