From: Eliot Moss <moss@cs.umass.edu>
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 07:30:03 -0500 [thread overview]
Message-ID: <2f9a63f8-37e3-5ea0-1541-608cf59faffa@cs.umass.edu> (raw)
In-Reply-To: <CAC+X2=L2tCUSUYreh2oTSt33Zn295Boru6eAPfkckksKXnB4vQ@mail.gmail.com>
On 1/4/2021 5:36 AM, Matt D. via Cygwin wrote:
> Did you try any of my test cases? This can't and doesn't work for the
> reasons I outlined in my previous message:
>
> $ cp -av folder_a/a folder_b/
> 'folder_a/a' -> 'folder_b/a'
> cp: cannot create symbolic link 'folder_b/a': No such file or directory
>
> $ cp -dv folder_a/a folder_b/
> 'folder_a/a' -> 'folder_b/a'
> cp: cannot create symbolic link 'folder_b/a': No such file or directory
>
> $ cp -Pv folder_a/a folder_b/
> 'folder_a/a' -> 'folder_b/a'
> cp: cannot create symbolic link 'folder_b/a': No such file or directory
So did you mkdir folder_b first? I don't think cp will create it for you. I
tried the commands above with folder_b not existing and got the behavior you
indicated, but when I created folder_b first, all three cp commands worked.
This overall behavior does not surprise me.
On the other hand, if I have folder_b non-existing and do (e.g.)
cp -rav folder_a folder_b
then it _does_ create folder_b, and also copies the links.
HTH - Eliot Moss
next prev parent reply other threads:[~2021-01-04 12:30 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 [this message]
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
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=2f9a63f8-37e3-5ea0-1541-608cf59faffa@cs.umass.edu \
--to=moss@cs.umass.edu \
--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).