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
Date: Thu, 22 Feb 2001 10:23:53 +0300
From: Egor Duda <deo AT logos-m DOT ru>
X-Mailer: The Bat! (v1.45) Personal
Reply-To: Egor Duda <cygwin AT cygwin DOT com>
Organization: DEO
X-Priority: 3 (Normal)
Message-ID: <21157045389.20010222102353@logos-m.ru>
To: Corinna Vinschen <cygwin AT cygwin DOT com>
Subject: Re: [ANNOUNCEMENT]: Important change to symbolic link functionality
In-reply-To: <20010221232921.X908@cygbert.vinschen.de>
References: <20010221232921 DOT X908 AT cygbert DOT vinschen DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hi!

Thursday, 22 February, 2001 Corinna Vinschen cygwin AT cygwin DOT com wrote:

CV> I want to announce a change to the symlink functionality of Cygwin
CV> which introduces an incompatibility when trying to revert to older
CV> versions of the Cygwin DLL.

CV> Currently symbolic links are files with the content

CV>         !<symlink>filename

CV> where filename is the name the symlink points to. Additionally
CV> the symlinks have the system bit set.

CV> The new version can still read this style of links but it creates
CV> a new style which is compatible to symlinks created by U/WIN.

CV> Symlinks are now Windows shortcuts (*.lnk files). They are created
CV> in a special format which is transparent to Windows Explorer and
CV> U/WIN.

i  haven't  looked  at new implementation yet, but i know at least one
problem  with  the  way  explorer  treats  .lnk  files.  if you create
shortcut  b.lnk pointing to file a.exe and then create (with explorer)
shortcut  c.lnk,  pointing  to  b.lnk, explorer automatically resolves
c.lnk  and make it point to a.exe! (Duh, that "optimizers" at microsoft
made a good "gift" to sysadmins)

Wouldn't it be a problem here? won't explorer spoil symlink-to-symlink
by just opening it? 

Egor.            mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple