From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 66686 invoked by alias); 24 Aug 2015 13:55:28 -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 66677 invoked by uid 89); 24 Aug 2015 13:55:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.6 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-qk0-f175.google.com Received: from mail-qk0-f175.google.com (HELO mail-qk0-f175.google.com) (209.85.220.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Mon, 24 Aug 2015 13:55:24 +0000 Received: by qkda128 with SMTP id a128so18032726qkd.3 for ; Mon, 24 Aug 2015 06:55:21 -0700 (PDT) X-Received: by 10.55.212.25 with SMTP id l25mr43779620qki.105.1440424521706; Mon, 24 Aug 2015 06:55:21 -0700 (PDT) Received: from [192.168.0.7] (d27-96-48-76.nap.wideopenwest.com. [96.27.76.48]) by smtp.gmail.com with ESMTPSA id r16sm5317482qkl.3.2015.08.24.06.55.20 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Aug 2015 06:55:21 -0700 (PDT) Subject: Re: 2.2.1: NTFS directory symlinks handling To: cygwin@cygwin.com References: <55D7C3E0.3020703@aosc.xyz> From: cyg Simple X-Enigmail-Draft-Status: N1110 Message-ID: <55DB2262.70408@gmail.com> Date: Mon, 24 Aug 2015 13:55:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <55D7C3E0.3020703@aosc.xyz> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2015-08/txt/msg00396.txt.bz2 On 8/21/2015 8:35 PM, Mingye Wang (Arthur2e5) wrote: > It is known that cygwin has a naive interpretation for NTFS symlinks, by > translating those paths directly. This works fine with most cases, but > when you link stuffs under `/` to somewhere like `../cygwin/home`, it > simply breaks. > > I have a directory tree like this: > > |- cygwin/ > |- home/ > |- Arthur/ > |- .gnupg/ (mklink /D .gnupg \Users\Arthur\Appdata\Roaming\gnupg) > |- .ssh/ (mklink /D .ssh \Users\Arthur\.ssh) > |- tmp/ > |- 1.txt > |- cygwin64/ > |- tmp@ (mklink /D tmp ..\cygwin\tmp) > |- home@ (mklink /D home ..\cygwin\home) > > It appears that those `.gnupg` and `.ssh` with an absolute path to the > drive root was interpreted correctly, like > `/cygdrive/c/Users/Arthur/.ssh`, but cygwin64's /tmp and /home breaks, > with the following manner described: > I would suggest to stick to absolute paths. What happens when you "dir ..\cygwin"? I.E.: Is it a valid path to begin with? -- cyg Simple -- 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