X-Recipient: archive-cygwin@delorie.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E45193896C37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1610474407;
	bh=5Llw+DJ0tRkFlx0lmQhOf3z0PwvDdttA6Kx1Re5/J6w=;
	h=References:In-Reply-To:Date:Subject:Cc:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	 From;
	b=GayKDzr+PUoAT0rRc0Gkrw27dr005Wo2CGTaBc3JL7H1ExECGcs6BAVqJymjZXEqH
	 U7BdH2QrI7nc1+aDgk66lLiCyGINqMXNFznnzd645t3ph+alBM69y6do367mx5ygl9
	 O8q8IDxl/pNrhoZUdvkgYT5fSAWJUCxLD5+BuBrI=
X-Original-To: cygwin@cygwin.com
Delivered-To: cygwin@cygwin.com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 5174F3896C14
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:cc;
 bh=f/1kkus40vztJwpbhFz/XmiMSbtpdr7shJIv1/ZGp6Q=;
 b=hkXkuvXd7YtZErkmj/PGYa9iROlHAITwIEf6FYpsNlfv+KEmR9X8eR4iUB+TOtl/m9
 dbr/2ou6FuISGr52qQMdP6jjD519rJR5ih7wyDBycXl6aUb7W8QaKISJmqPou9UOvPLu
 8J54h6XGEo2/NS1sjF/meaXHjv4Ra93AzhJxnXcgBH4cB1mLmLv43hQPKSSD5X0W78kX
 kCn+evSD9h/mvkiFBTTBkbu3D2axBSbvwXtNdqVmUX8fA+ZMShH+87S7YCQUmw6gZ3Us
 HhGHWIw5cUHiIVnt4tLFDnrxGzp+p0WPCacVMQbSfHG/cMCtpjWMTjnm6z8yztgmSCHF
 /CNw==
X-Gm-Message-State: AOAM532+VQl0vWF727NdL7O/8cYg2B4Mb3SpN4nZeznhu9jxpbdSgueQ
 9gARCegl/lijnWY69q8JcB5qFNDMWvWukIaFfVuOMgC4vUs=
X-Google-Smtp-Source: ABdhPJzHzGUy2i8yCUefr6aJolaN5h7En2lX/ptikmAfCwh3xHuXfOBr2kvBeNc7NBFLyoQz+f9avHZwUemf2ZRoHQc=
X-Received: by 2002:a19:e8e:: with SMTP id 136mr63230lfo.272.1610474401607;
 Tue, 12 Jan 2021 10:00:01 -0800 (PST)
MIME-Version: 1.0
References: <CAC+X2=J-mKZH7WAdt2RQocqP+4rUqSkGi-acDC7U3N=uu7QGDA@mail.gmail.com>
 <1d853aa0-4cbe-b92c-8d9f-53fc72371a7b@SystematicSw.ab.ca>
 <CAC+X2=L2tCUSUYreh2oTSt33Zn295Boru6eAPfkckksKXnB4vQ@mail.gmail.com>
 <2f9a63f8-37e3-5ea0-1541-608cf59faffa@cs.umass.edu>
 <CAC+X2=L-sBmgi_OoFVjJtpPp6MszHGH8ycEiOo4V1NNbWDAP-A@mail.gmail.com>
 <89f9e340-367f-e2c0-18da-d433379c0c9b@secure-endpoints.com>
In-Reply-To: <89f9e340-367f-e2c0-18da-d433379c0c9b@secure-endpoints.com>
Date: Tue, 12 Jan 2021 12:59:49 -0500
Message-ID: <CAC+X2=J5VunWyU1-v3uyCeam2nh6y9SG6D4ech+-aJfWUt2LDQ@mail.gmail.com>
Subject: Re: Native symbolic link behavior is broken and makes backups using
 Cygwin command line tools impossible
Cc: cygwin@cygwin.com
X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_00, DKIM_SIGNED,
 DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, MALFORMED_FREEMAIL,
 MISSING_HEADERS, RCVD_IN_DNSWL_NONE, 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
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: "Matt D. via Cygwin" <cygwin@cygwin.com>
Reply-To: "Matt D." <codespunk@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces@cygwin.com>

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.


On Mon, Jan 4, 2021 at 10:46 AM Jeffrey Altman via Cygwin
<cygwin@cygwin.com> wrote:
>
> On 1/4/2021 10:27 AM, Matt D. via Cygwin (cygwin@cygwin.com) 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.
>
> I hope this knowledge helps.
>
> Jeffrey Altman
>
>
>
>
>
> --
> 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
--
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
