This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [ANNOUNCEMENT] Updated: zsh-4.2.0-1

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.
      |\      _,,,---,,_
ZZZzz /,`.-'`'    -.  ;-;;,_
     |,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:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]