From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 56844 invoked by alias); 18 Nov 2015 17:55:09 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 56829 invoked by uid 89); 18 Nov 2015 17:55:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-5.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 X-HELO: calimero.vinschen.de Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 18 Nov 2015 17:55:06 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id C4A19A806A4; Wed, 18 Nov 2015 18:55:03 +0100 (CET) Date: Wed, 18 Nov 2015 17:55:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Symlink targets dereferenced when winsymlinks:native Message-ID: <20151118175503.GT6402@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <564BAA1A.8000703@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="AptwxgnoZDC4KQWS" Content-Disposition: inline In-Reply-To: <564BAA1A.8000703@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-11/txt/msg00252.txt.bz2 --AptwxgnoZDC4KQWS Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1173 On Nov 17 23:28, David Macek wrote: > Hi. >=20 > 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. It's a result of the native symlink being a Windows path. The ultimate conversion from POSIX to Windows path dereferences all symlinks. > That doesn't happed when > using regular symlink files. Is this behaviour intentional / known? >=20 > If it matters, the use case is `ln -sf /proc/self/fd /dev/fd`. It matters. This is a bug in Cygwin, a missing test in fact. It should never allow to create native symlinks to targets which only exist inside of Cygwin. Consider that /proc/self/fd has no meaning to non-Cygwin processes at all. Creating this symlink as native symlink doesn't make any sense, they should always be generated as Cygwin-only symlinks. Thanks for the report, I'll apply a matching patch. Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --AptwxgnoZDC4KQWS Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWTLt3AAoJEPU2Bp2uRE+g+ucP/A3l+TIzSKLhegA42E0xUnHZ 3HUQxSRXMNIWkK4PZ3bAgBBlsNQmWKFL4AZXyRI1yHnep6pcTDNCgZYHvOgg0keC j3NT8vERSjzMxp7vh+B21j36oV33avfa5ga7p3zUxARbgF3HhTbN6sdQ57coslE6 0xuDT3xZfkNYy/rGx7kRQ6tN0n3pW2gXQ0WWbnIHzgUXl38UZZSA6ikoUtVbwqd7 VsaMzbIok427GvitIntnJoO0CsEcKyTUfy2RRymudnx17FfL1qWDpRnJvWU1WWUl VdDCopMfb1ewc/ccICwWP8ComW/Ewwq1luicg95G5kAb3YGy9DrzVWjyXhcSLP6C n4rNGHqzwRhZ8vL8EeeVr01VICLbLR0WkRXcn4SDR6lkhKQdVDsBs7902V3hbe9z 2EETiVTlxze41LXoJ9fmQsfc0FH64sdB76WzBt9BBdRYjJMu7maG0DFrQAXNou5t MtSTWH94V3WfXm0TtkZq6HUMQm5qFruKqqqntyfWOpIScxcqhaVMAwGoIx7oJzL8 Xdmqw74wnaftdPgAQEPEOmH2P5SbbwOxpTx4iBHlzvCeERcz0WL3fh5Y/AhzUCag VTh1ChtnfQvh+Q8nA4ObiNDz2ITx9yFDu34KW/01NyElSvAqiyIlfKQX43MzLF60 7xGxZuq4hO/NejfSI1Bl =tIAW -----END PGP SIGNATURE----- --AptwxgnoZDC4KQWS--