From: David Macek <david.macek.0@gmail.com>
To: cygwin@cygwin.com
Subject: Symlink targets dereferenced when winsymlinks:native
Date: Tue, 17 Nov 2015 22:28:00 -0000 [thread overview]
Message-ID: <564BAA1A.8000703@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Hi.
I went through the UG looking for differences between regular Cygwin symlinks and NTFS symlinks, but couldn't find this documented. It seems that when using winsymlinks:native, the target path is first dereferenced before storing it in the link. That doesn't happed when using regular symlink files. Is this behaviour intentional / known?
If it matters, the use case is `ln -sf /proc/self/fd /dev/fd`.
--
David Macek
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4254 bytes --]
next reply other threads:[~2015-11-17 22:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 22:28 David Macek [this message]
2015-11-18 17:55 ` Corinna Vinschen
2015-11-18 18:13 ` David Macek
2015-11-18 19:48 ` Corinna Vinschen
2015-11-18 20:01 ` Warren Young
2015-11-18 20:07 ` Corinna Vinschen
2015-11-19 18:53 ` David Macek
2015-11-19 19:36 ` Nellis, Kenneth
2015-11-19 21:17 ` David Macek
2015-11-20 9:26 ` Corinna Vinschen
2015-11-24 21:48 ` David Macek
2015-11-26 12:02 ` Corinna Vinschen
2015-11-29 14:10 ` David Macek
2015-11-29 17:10 ` Corinna Vinschen
2015-11-20 9:29 ` Corinna Vinschen
2015-11-24 19:51 ` David Macek
2015-11-25 3:20 ` Linda Walsh
2015-11-25 14:59 ` David Macek
2015-11-26 11:53 ` Another reason to not corrupt winnative symlinks: :currenly, they are linux-CIFS compat. Cygwin's are not Linda Walsh
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=564BAA1A.8000703@gmail.com \
--to=david.macek.0@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).