Earl Hood <[EMAIL PROTECTED]> writes:
> On March 4, 1999 at 21:26, Stephen Wilson Bailey wrote:
> > Finally, symlinks can't be created, so the installation part of
> > commands that are symlinks doesn't work. Furthermore if copies are
>
> What parts of creating symlinks fail? From my observation, Cygwin
> supports symbolic links.
It's been a while since I played with Cygwin32, but were symbolic links an
optional feature that you can disable (or have to explicitly enable)?
Since there's no Win32 support for symbolic links, it implements them by
putting a magic string at the beginning of symbolic link files and having
the Cygwin library routines always look for that string to determine whether
the file is a link or not. All this extra I/O (and the potential for
incorrect symbolic link determination) would explain why they'd be
optional...
---------------------------------------------------------------
Dan Harkless | To prevent SPAM contamination, please
[EMAIL PROTECTED] | do not post this private email address
Unitech Research, Inc. | to the USENET or WWW. Thank you.
