DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=Po
	ldKxRhl5tUEIcNwgH88W5o5TMVfKYfZVOvvZ3w31xUe9IBvKzkabqoR6+tI+hrVa
	INcl5/yKgyJ/NqFF7eBpIe0cDJK0yVDT/G+8YWTXDv3jj79TCtZC24fAz5vCXLKz
	gYcMKZ5oxJ//cT8LUuXaG05Yat4TXki/Uub20fb8s=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <1606116423.20160429020650@yandex.ru>
References: <CAPTiy3NUXprQL6V0+Njc2L7XfhpqtC7oWFwNMhOEFZ2OZmddoQ@mail.gmail.com>	<1606116423.20160429020650@yandex.ru>
Date: Fri, 29 Apr 2016 14:34:18 +0300
Message-ID: <CAPTiy3OhkvWhGKCisnoLBFZqTL1_Rcq4-vdn0U8Qfnxk+WsX-A@mail.gmail.com>
Subject: Re: `CYGWIN=winsymlinks:nativestrict`, `ln -s target link` fails if target doesn't exist
From: Gene Pavlovsky <gene.pavlovsky@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

> > POSIX says a symlink to a missing target is perfectly well-defined (you
> > can't stat() through it, but you can readlink() it). But Windows native
> > symlinks can't do that.  So the problems you are encountering all stem
> > from the fact that you are trying to make Windows do something it can't.
>
> My initial reaction was that, too, but I tried mklink (CMD internal command)
>
> > mklink x y
>
> and it created the symlink in the empty directory just fine.

This is my point exactly. Windows dangling symlinks can be created as
easily as in UNIX.
At least this is the case on my Win7 x64.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple