From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from forward103p.mail.yandex.net (forward103p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:106]) by sourceware.org (Postfix) with ESMTPS id 61F783899435 for ; Tue, 12 Jan 2021 22:20:04 +0000 (GMT) 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@yandex.ru Received: from sas1-6b94a3a85f37.qloud-c.yandex.net (sas1-6b94a3a85f37.qloud-c.yandex.net [IPv6:2a02:6b8:c14:3924:0:640:6b94:a3a8]) by forward103p.mail.yandex.net (Yandex) with ESMTP id 44DBE18C06DA; Wed, 13 Jan 2021 01:20:02 +0300 (MSK) Received: from sas1-e20a8b944cac.qloud-c.yandex.net (sas1-e20a8b944cac.qloud-c.yandex.net [2a02:6b8:c14:6696:0:640:e20a:8b94]) by sas1-6b94a3a85f37.qloud-c.yandex.net (mxback/Yandex) with ESMTP id 5OqkUYBWgC-K2DW4WjP; Wed, 13 Jan 2021 01:20:02 +0300 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 Received: by sas1-e20a8b944cac.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id Fqs79G5J99-K1J48djd; Wed, 13 Jan 2021 01:20:01 +0300 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client certificate not present) Received: from [192.168.1.10] (HELO daemon2.darkdragon.lan) by daemon2 (Office Mail Server 0.8.12 build 08053101) with SMTP; Tue, 12 Jan 2021 22:18:03 -0000 Date: Wed, 13 Jan 2021 01:18:03 +0300 From: Andrey Repin X-Mailer: The Bat! (v6.8.8) Home Reply-To: cygwin@cygwin.com X-Priority: 3 (Normal) Message-ID: <251301264.20210113011803@yandex.ru> To: "Matt D." , cygwin@cygwin.com Subject: Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible In-Reply-To: References: <1d853aa0-4cbe-b92c-8d9f-53fc72371a7b@SystematicSw.ab.ca> <2f9a63f8-37e3-5ea0-1541-608cf59faffa@cs.umass.edu> <89f9e340-367f-e2c0-18da-d433379c0c9b@secure-endpoints.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Jan 2021 22:20:06 -0000 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...