X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 61F783899435
Authentication-Results:	sourceware.org;
	dmarc=pass (p=none dis=none) header.from=yandex.ru
Authentication-Results:	sourceware.org;
	spf=pass smtp.mailfrom=anrdaemon AT yandex DOT ru
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail;
	t=1610490002; bh=C5juPj3bRXqj9cPB+jgaJW7CB0rw0Ox+Pd44ajfnaOg=;
	h=In-Reply-To:Subject:To:From:Message-ID:References:Date:Reply-To;
	b=D1idLpf2bP85LPjpV2ZFAv5Ge2uGXGI5CGvFhmPr/6KkY9Qd9JmX4MnOZWaotBTTf
	+dxdqjxiIqyW7cOf62j7j5efch4nZqJIFKY/gTPDPxxNGzCT600cJj2iXt9zWAJ+v2
	Ahef5VzGIIlX7r7OpB3odpPzu6wn4UHgXx91/LtA=
Authentication-Results:	sas1-6b94a3a85f37.qloud-c.yandex.net;
	dkim=pass header.i=@yandex.ru
Date:	Wed, 13 Jan 2021 01:18:03 +0300
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
X-Mailer:	The Bat! (v6.8.8) Home
X-Priority:	3 (Normal)
Message-ID:	<251301264.20210113011803@yandex.ru>
To:	"Matt D." <codespunk AT gmail DOT com>, cygwin AT cygwin DOT com
Subject:	Re: Native symbolic link behavior is broken and makes backups using
	Cygwin command line tools impossible
In-Reply-To:	<CAC+X2=J5VunWyU1-v3uyCeam2nh6y9SG6D4ech+-aJfWUt2LDQ@mail.gmail.com>
References:	<CAC+X2=J-mKZH7WAdt2RQocqP+4rUqSkGi-acDC7U3N=uu7QGDA AT mail DOT gmail DOT com>
	<1d853aa0-4cbe-b92c-8d9f-53fc72371a7b AT SystematicSw DOT ab DOT ca>
	<CAC+X2=L2tCUSUYreh2oTSt33Zn295Boru6eAPfkckksKXnB4vQ AT mail DOT gmail DOT com>
	<2f9a63f8-37e3-5ea0-1541-608cf59faffa AT cs DOT umass DOT edu>
	<CAC+X2=L-sBmgi_OoFVjJtpPp6MszHGH8ycEiOo4V1NNbWDAP-A AT mail DOT gmail DOT com>
	<89f9e340-367f-e2c0-18da-d433379c0c9b AT secure-endpoints DOT com>
	<CAC+X2=J5VunWyU1-v3uyCeam2nh6y9SG6D4ech+-aJfWUt2LDQ AT mail DOT gmail DOT com>
MIME-Version:	1.0
X-Spam-Status:	No, score=-2.1 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_THEBAT,
	NICE_REPLY_A, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS,
	TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To:	cygwin AT cygwin DOT com
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

Greetings, Matt D.!

Please no top posting in this list.

> On Mon, Jan 4, 2021 at 10:46 AM Jeffrey Altman via Cygwin wrote:
>>
>> On 1/4/2021 10:27 AM, Matt D. via Cygwin wrote:
>> > I am using symbolic links native to Windows. My CYGWIN environment
>> > variable has been set to "winsymlinks:nativestrict" and my account has
>> > permission to make symbolic links. This is an issue specifically with
>> > Cygwin; I have no problems making links at the windows command line.
>> > Cygwin also does not have a problem making symbolic links-- if the
>> > target already exists. The issue is that I cannot create native
>> > symbolic links with Cygwin for targets that DON'T exist.
>> >
>> > The normal behavior for both Windows and Linux is to create the
>> > symbolic link whether the target exists or not. I don't know why
>> > Cygwin fails to do this only for native Windows symbolic links. It
>> > does not have a problem creating links to any target with the default
>> > Cygwin (non-Windows) symbolic links.
>>
>> Windows native symlinks encode the object type of the target and the
>> encoded type must match that of the target or the link will not work
>> when the target exists.
>>
>> A UNIX symlink does not encode any details of the target.
>>
>> Cygwin doesn't know what type of native symlink to create if the
>> target does not exist.

> Operations like cp and rsync etc. should still work. The type of
> symbolic link to be created can be read from the file attributes of
> the one being copied.

Again, the properties are read BY SYSTEM at the moment the link is created.
In other words, Windows is unable to create a link to nonexistent
(unreachable) target (not directly, at least).


-- 
With best regards,
Andrey Repin
Wednesday, January 13, 2021 1:14:52

Sorry for my terrible english...

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

- Raw text -