X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 539A1388CC14 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1622229801; bh=SKC9QtkJWulgYBe45EtG2gx4BEPHdFe51eUWLMyCR/o=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=GAn9AGmrGkL7lS2lzNwnvcmfzO99QAPWycThj2FY2/utpiENObWMLtAT3HhfQfClq lMpstL1+lidOZfKiZfFDBL5fAMvBbrye2xmwbMKxy6WnTEBD30bBfpauXR3RPmSkOc 4kOnT1zvvsxfAzlDqxsCrIbloh5NZLcoY0OWRMhM= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org CEE83388CC0D Date: Fri, 28 May 2021 12:23:17 -0700 (PDT) X-X-Sender: jeremyd AT resin DOT csoft DOT net To: cygwin AT cygwin DOT com Subject: Re: realpath issue with native[strict] symlinks In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (BSO 202 2017-01-01) MIME-Version: 1.0 X-Spam-Status: No, score=-6.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, SPF_HELO_PASS, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Jeremy Drake via Cygwin Reply-To: Jeremy Drake Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" On Thu, 27 May 2021, Jeremy Drake wrote: > > > Treating mapped/subst drives as though they were not symlinks, without > > > messing with intermedate symlinks. > > > > It was that simple, surprise, surprise... > > It turns out it wasn't, after all. This only seems to work at the root of > a subst-ed drive. I just got the following error: I was thinking about this more, and maybe I'm fixated on the wrong code (since that code change "broke" it). Perhaps SUBST drives *should* be treated as native symlinks, and what needs to change is that native symlinks should not be dereferenced when launching native programs. I assume the symlink-dereferencing there predates the native symlink support, and was required since native programs wouldn't be able to traverse a cygwin symlink or .lnk file. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple