X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BFB5E388A77E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1670847148; bh=UMcUmdNWlprZB5z8kLfk4Yl/c8ikh2xYX3YC5JzyiZs=; h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=X2Zcev9eOTXQevhu3YIxMqcKqS9OwJAGoGwn346cJ2/Yx/8uBkuLK9ES41ixpYJVw HFlcSlxWgA6P9aPhGGN1IbVBjbAotxIS7F4YbhRiycRVcJomwrrbsPRI3zLVNofQaL L+mJXypiP92byy00UOuelZNa/v0kcsybsejVyvq0= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com Date: Mon, 12 Dec 2022 13:12:10 +0100 To: Frank Redeker Subject: Re: Strange behavior when executing programs Message-ID: Mail-Followup-To: Frank Redeker , cygwin AT cygwin DOT com References: <1031eafe-fc3b-ab5b-6e63-b0f56c038332 AT razorcat DOT com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1031eafe-fc3b-ab5b-6e63-b0f56c038332@razorcat.com> X-Provags-ID: V03:K1:RC00dOk5bG3ARJ2UYBqEPYbQ9728Ma/ZcD3LqikSdMl8aAqvMTG TVBSBIGAzNNaQDbAaPvJGhtwJETNDGXkkSee1uZR8c2K594bbZuujQToeCkXoiKpArquZ9V MYQLj2cENsTOuv0P7pC7pnBKNHvbOw+VVp4bHTNE54AFeZ9utVExIics9gjjcgxIdV7+bP6 CFPUHqCcH2v6jOqB3HwVw== UI-OutboundReport: notjunk:1;M01:P0:43eyoWwnsH4=;kHE4Mn0IOMTvbLtvdcZJytUoMKP 644abe+e3ZIuXU5ihsHlkCxASpGMFJ++7V7EQc/Q3Pk5jL6RwAraENxC2Lj3vC1Bd4mzmv6aR LBDmuje6Z9Wfje4MucRaJFgOqU6v5cnxZ+CvKBQTUYZFqbfkcr/eIJgAkt2mOAAeCI4vMVSNb DFbgx2gKS8Nsk1fK1ne87t8bBmnTCARSlZbZIJ2Lh/t9DifM/GYqsTXKYrdCDj3P0e/Wf7lv6 vHj3m8CXWT21NMbsLC0NHUX6TTF1HN9+AZrtJPI9DT60BmvSTcWBn7Ui+mOu5iDHALEI1gmaq iDBlhnbs9KUAAHX0UgPeSAYmJQl3IHxm94rKiu4Lv02utOV2O1QeGMU6q2X9Xk+oQ8AJg9+a0 VMfphKy6EePgc29bFUtbyyjYwTpjBGwuipm5UJeWVmxliSJW2c5Bt+Oag1AY4CEIZvqHZqWp6 5tWKr/JQDfyXNecoPxRLdyYwlFg0bs0RuqNYAsnMQp34Jl2lYEWYENf2xMw5b33jzn6p37FrS sg0E5wWXhU2l6xwFnOOFq0HDAdr8pWP6RHPMGOAAr0p2KQCBSgPBWqg+u3cQ1rgHoCZXW6isV Nm9OU3SvKkPn/vZzoPdoj43EVv17XP6RIeCvky/rh+4kdxykgnU9O2eQUvQ2JzjaZrHxVRao7 bHj0IDPMvar6WIGzfFwhzxjty3QFfAeaRKBJyqGYtg== X-Spam-Status: No, score=-95.5 required=5.0 tests=BAYES_00, GOOD_FROM_CORINNA_CYGWIN, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) 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: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen , cygwin AT cygwin DOT com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" On Dec 12 11:21, Frank Redeker via Cygwin wrote: > $ pwd > /cygdrive/s/ado > > $ realpath /cygdrive/s/ado/msadox.dll > /cygdrive/s/ado/msadox.dll > > $ realpath msadox.dll > /cygdrive/c/Program Files/Common Files/System/ado/msadox.dll > > > Is there any way to restore the old behavior. Since with the new behavior my > tests no longer work. It's not easy. If we remove the new behaviour entirely, we break other scenarios which were broken in the old version. While it *seems* easy to fix your specific scenario, it will break again as soon as the substitution drive is used inside a native symlink. Virtual drive letters were always a problem and it doesn't get easier with Windows functions not allowing to specify whether one wants to follow symlinks or virt drives in inner path components or not. Let's consider this problem again, but I don't see a quick and easy solution. Corinna -- 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