This is the mail archive of the
mailing list for the Cygwin project.
Re: Cygwin and Vista symlinks using mklink problem
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 12 Mar 2008 09:48:46 +0100
- Subject: Re: Cygwin and Vista symlinks using mklink problem
- References: <C8AB7E937E88451CA95B9939088C9DFC@PaulCarewCRC>
- Reply-to: cygwin at cygwin dot com
On Mar 11 22:12, Paul Carew wrote:
> I have noticed that Cygwin and the new Vista command 'mklink' do not
> co-exist very happily.
> If you create a Vista symlink using mklink and then try to delete/remove
> it using 'rm', the target is deleted and not the symlink!
Cygwin 1.5.25 does not recognize the new native NTFS symlinks as
symlinks. For a Cygwin process, the native symlink is a normal file and
opened and handled like a normal file. The fact that unlink removes the
target of the symlink instead of the symlink is an unfortunate Window'ism.
The next major version of Cygwin will recognize native NTFS symlinks as
symlinks, so that won't happen anymore. However, Cygwin will not
utilize NTFS symlinks for its own symlinks, because the native symlink
functionality has two serious flaws:
- By default, only administrators have the right to create native
symlinks. Admins running with restricted permissions under UAC don't
have this right.
- When creating a native symlink, you have to define if this symlink
points to a file or a directory. This makes no sense given that
symlinks often are created before the target they point to.
These issues make native symlinks almost unusable from a POSIX
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html