This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
Re: [ANNOUNCEMENT]: Important change to symbolic link functionality
- To: Corinna Vinschen <cygwin at cygwin dot com>
- Subject: Re: [ANNOUNCEMENT]: Important change to symbolic link functionality
- From: Egor Duda <deo at logos-m dot ru>
- Date: 2001年2月22日 10:23:53 +0300
- Organization: DEO
- References: <20010221232921.X908@cygbert.vinschen.de>
- Reply-To: Egor Duda <cygwin at cygwin dot com>
Hi!
Thursday, 22 February, 2001 Corinna Vinschen cygwin@cygwin.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@logos-m.ru ICQ 5165414 FidoNet 2:5020/496.19
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple