Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <03F4742D8225D21191EF00805FE62B9908E23ECD@aa-msg-01.medstat.com>
From: John Wiersba <John DOT Wiersba AT medstat DOT com>
To: "'cygwin'" <cygwin AT sourceware DOT cygnus DOT com>
Subject: Symbol link trouble ?
Date: Tue, 26 Jun 2001 18:27:43 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 26 Jun 2001 22:27:58.0014 (UTC) FILETIME=[405F4DE0:01C0FE8F]

Searching the archives for info on symlink weirdness, I found the following
reference with the same subject as above:

http://sources.redhat.com/ml/cygwin/2001-04/msg01545.html which contains
this:

> Secondary questions:
>    are these cygwin links supposed to be Win95 compatible ?
> Because the Windows file explorer does tell em
> that these files are Shortcuts
> but the destination file is empty if I Right klick on the file and select 
> properties!

This seems to indicate that this bug only happens on Win95, but I've seen
this same behavior on WinNT.  The really weird thing is that some of my
shortcuts have been OK and others are not (as described above).  I have a
script which removes and recreates the symlinks I use to set up my
environment, and at the moment all of them are OK.  But I probably could
reproduce this if it would help.  Also, from Windows Explorer I believe I've
seen that the OK symlinks are shown as folder shortcuts but the broken ones
are shown as file shortcuts.  However, all of the symlinks (even the broken
shortcut ones) worked under cygwin -- it was only under WinNT that I noticed
any difference.  Also, I noticed that I couldn't fix the target path of the
broken shortcut (via Properties) because it seemed to be locked by WinNT.

-- John Wiersba

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/