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: Wed, 7 Apr 2004 21:51:54 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] Updated: zsh-4.2.0-2 Message-ID: <20040408015154.GA3897@coc.bosbc.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20040407152041 DOT AF6F5400155 AT timesys DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-OriginalArrivalTime: 08 Apr 2004 01:50:59.0973 (UTC) FILETIME=[F114BB50:01C41D0B] On Wed, Apr 07, 2004 at 06:40:57PM -0700, Peter A. Castro wrote: >*grumble* Hmm... I suspect this is really a Setup issue. The binary >is stored in the tar as a hardlink to the versioned name. If you >manually unpack it, with tar, it does the right thing. On an NTFS >volume, it makes it a hardlink to the real file (ie: link count = 2). >On a FAT volume, it duplicates the file's contents (ie: link count = >1). It appears setup isn't quite handling it correctly for your >configuration. We'd have to get detailed info about your config. Are >you using the latest setup.exe, btw? If not, try a snap-shot first. >It's as simple a un-installing and re-install zsh to test. Again, setup.exe does not understand hard links. So if you use a hard link in your tar file, you will not get a hard link when setup.exe installs it. 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/