From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 122642 invoked by alias); 18 Nov 2015 19:48:24 -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 122631 invoked by uid 89); 18 Nov 2015 19:48:23 -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 19:48:22 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 65381A806A4; Wed, 18 Nov 2015 20:48:19 +0100 (CET) Date: Wed, 18 Nov 2015 19:48:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Symlink targets dereferenced when winsymlinks:native Message-ID: <20151118194819.GV6402@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <564BAA1A.8000703@gmail.com> <20151118175503.GT6402@calimero.vinschen.de> <564CBFCC.4020605@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="KaGhPsiNaI6/sRd6" Content-Disposition: inline In-Reply-To: <564CBFCC.4020605@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-11/txt/msg00255.txt.bz2 --KaGhPsiNaI6/sRd6 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1241 On Nov 18 19:13, David Macek wrote: > On 18. 11. 2015 18:55, Corinna Vinschen wrote: > > On Nov 17 23:28, David Macek wrote: > >> 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. > >=20 > > It's a result of the native symlink being a Windows path. The > > ultimate conversion from POSIX to Windows path dereferences all > > symlinks. >=20 > Should that behaviour stay? Yes. Consider that neither Cygwin or Interix symlinks with SYSTEM bit set, nor symlinks using WIndows shortcuts make any sense as part of a native symlink. As a result, Cygwin does a full path conversion from POSIX to symlink-less Windows path to crate native symlinks. > If not, I can send a patch for the UG. UG? > > Thanks for the report, I'll apply a matching patch. >=20 > Cool. https://sourceware.org/git/?p=3Dnewlib-cygwin.git;h=3D8cdd7bad219ba2657e381= bd0d716594c50a6ef62 Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --KaGhPsiNaI6/sRd6 Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWTNYDAAoJEPU2Bp2uRE+g9sQP/i5yJE38QL2W04ZpgPtjRYu/ TZ/PpA7SqJ4iX1vuvZR1bk0aQtPHP2QQz2bcjJVw2CVHKYvZOrEIixzz8o+iaIkp D/VtBVFeD7Fvwd0x/MJY3jTLQQVoA+5Pw5KVinWpwnLbcwDclVXW833aCX4N0mU1 p54AvZ6rc+FcL4tvy/VGHTFkDX2Nkwq+RlnrzXVK34V63aR+lWwLP92IvfYK9b7w w5Jg+6OCTKhedCOhM/7o132xwtnt7yn3KelAxZk83q2t6Hy6MM9A++NTwCM+7+/m tZXG/+tk+Ghefw1FYfUuot3cfur7IXfW4L+04pVJizrBszVT1bNpO4bo9xNYJ1C7 TwJ5pcotlsburY09O34Ovii1SRZSemd8oF9I5CvD8skZY4rhT8gK6xEOaBWqpLJ3 TwF2L3R7mRhV45OIpW2KUvnSISKjD1IBboyAenqurFip2I52KhW37lXC3nCnW415 F1dv8zfzOCGDHT1OlNXNKZ/OpdQM6zDcE2QliRD4eAafcnfYeFYcV4eXP/t2BrFm fO5lVdhBZqeoKnxlRf0HXtVatg1USq1S6eOXCs7ID+ppuzGHrALiMzAFQvS3wTR1 o6K7vD3dATDk4Bk4b5wc94PDoC9pIU4cHERoe/vT1R+JyCVkTsx+rjbht9HmbnlS 4EX5hUKaDxw4xfojiEj+ =K6gl -----END PGP SIGNATURE----- --KaGhPsiNaI6/sRd6--