From: Andrey Repin <anrdaemon@yandex.ru>
To: "Matt D." <codespunk@gmail.com>, cygwin@cygwin.com
Subject: Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible
Date: Wed, 13 Jan 2021 01:18:03 +0300 [thread overview]
Message-ID: <251301264.20210113011803@yandex.ru> (raw)
In-Reply-To: <CAC+X2=J5VunWyU1-v3uyCeam2nh6y9SG6D4ech+-aJfWUt2LDQ@mail.gmail.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...
next prev parent reply other threads:[~2021-01-12 22:20 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
2021-01-12 17:59 ` Matt D.
2021-01-12 22:18 ` Andrey Repin [this message]
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=251301264.20210113011803@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=codespunk@gmail.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).