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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Wed, 31 Mar 2004 09:08:11 -0500 (EST) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Dave Korn cc: cygwin AT cygwin DOT com Subject: RE: [ANNOUNCEMENT] Updated: zsh-4.2.0-1 In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Wed, 31 Mar 2004, Dave Korn wrote: > > -----Original Message----- > > From: cygwin-owner On Behalf Of Peter A. Castro > > Sent: 30 March 2004 19:45 > > > The original issue was with the executable /usr/bin/zsh being > > a link to the real exe (eg: zsh-4.2.0). However, this is not > > a packaging error, IMHO. /usr/bin/zsh is a *hardlink*, not a > > *symlink*, > > Does that even work on 9x/ME series? I thought hardlinks required NTFS > support. True hardlinks do. Cygwin's "ln" simply copies the file if hardlink support is not available (e.g., on FAT*). I believe setup always copies the hardlinked file (looking at io_stream_cygfile::mklink), but this functionality is not extensively tested (e.g., zsh is the only binary tarball with a hardlink in it, AFAIK), so I wouldn't be surprised if something does go wrong. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- 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/