From: Andrey Repin <anrdaemon@yandex.ru>
To: Adrian H <adrianh.bsc@gmail.com>, cygwin@cygwin.com
Subject: Re: Using cp converts windows junctions to a cywin symlink
Date: Mon, 02 Nov 2015 20:05:00 -0000 [thread overview]
Message-ID: <1667216939.20151102225151@yandex.ru> (raw)
In-Reply-To: <CAP_kE8XU_sr2wrfvFQ1o8NrKrWvOZwU02+2CZbtkgtDD9H9R7A@mail.gmail.com>
Greetings, Adrian H!
> I was copying a directory of files, some of which were windows junctions.
> These got converted to a cygwin symlink. Although I am impressed that there
> are such a thing for those OSs/drives that do not support such things, for those
> that do, I think it would be good to keep the copy a junction. Otherwise,
> things can get messy.
> Can this be corrected?
Unfortunately, even on systems, that do support symlinks functionality, it is
restricted by UAC and not easily unlocked.
You'd need an admin shell or a user profile with UAC turned off and permissions
correctly configured to exploit native symlinks.
And Cygwin does not support creation of directory junctions to the best of my
knowledge. :(
--
With best regards,
Andrey Repin
Monday, November 2, 2015 22:48:43
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-11-02 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 18:57 Adrian H
2015-11-02 20:05 ` Andrey Repin [this message]
2015-11-02 23:32 ` Using cp converts windows junctions to a cywin symlink; a security-config override Linda Walsh
2015-11-02 23:50 ` Andrey Repin
2015-11-03 13:20 ` Using cp converts windows junctions to a cywin symlink Corinna Vinschen
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=1667216939.20151102225151@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=adrianh.bsc@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).