From: Jeffrey Altman <jaltman@secure-endpoints.com>
To: cygwin@cygwin.com
Subject: Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible
Date: Mon, 4 Jan 2021 10:46:07 -0500 [thread overview]
Message-ID: <89f9e340-367f-e2c0-18da-d433379c0c9b@secure-endpoints.com> (raw)
In-Reply-To: <CAC+X2=L-sBmgi_OoFVjJtpPp6MszHGH8ycEiOo4V1NNbWDAP-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1257 bytes --]
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
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4080 bytes --]
next prev parent reply other threads:[~2021-01-04 15:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 4:16 Matt D.
2021-01-03 5:00 ` Brian Inglis
2021-01-04 10:36 ` Matt D.
2021-01-04 12:30 ` Eliot Moss
2021-01-04 15:27 ` Matt D.
2021-01-04 15:46 ` Jeffrey Altman [this message]
2021-01-12 17:59 ` Matt D.
2021-01-12 22:18 ` Andrey Repin
2021-01-14 0:09 ` Matt D.
2021-01-04 16:32 ` Eliot Moss
2021-01-04 17:58 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=89f9e340-367f-e2c0-18da-d433379c0c9b@secure-endpoints.com \
--to=jaltman@secure-endpoints.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).