X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0B19F389245F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1619023668; bh=29+npt0srFU4aq6XHtRLCk0+kZWxOaaOdkOrykGhp4s=; 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=LDVCpPdeshXGSIfvT5ZehhSGCJjhzR+Z3YdV5R160YHSM9JTdTDnpQBQhCiyb2nB9 hXo1grzJ6nyLwJER/6tPM4D66ZawPIWVCzBwpak+GaoS/7OVjYPFxY2c6b2kaxdJ1u 1JJEihsManl6VZDuwIwF68R2CKaODIKP7rY291WU= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org CEB1A38460A2 Date: Wed, 21 Apr 2021 18:47:42 +0200 To: cygwin AT cygwin DOT com Subject: Re: Cannot access system32 directory from 32 bit cygwin after the commit 456c3a46 Message-ID: Mail-Followup-To: cygwin AT cygwin DOT com References: <20210421120457 DOT cd5b6e966288aa62eee1a013 AT nifty DOT ne DOT jp> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-Provags-ID: V03:K1:VmKffltAty/OCuVSHHqR7rrTbzsdQ8gssxS2thYHGEZjkruj2X4 Qvnpe7mw4V4cflTE9Rq8+0U9tFlKZHhN39R9hBY2oqrYmu6jOFHTgj+L3VyT+6T5PNF+/Jq GQscXykqc6JiCyc5H07PyXZAoUq0fd5dYMlX7+0VY+ttKYJCNGYI2OsaXwY0fM6Wi2ygfXu /ZsS7+XeWbEvFpB0nGMNg== X-UI-Out-Filterresults: notjunk:1;V03:K0:ckHK90Cjtgg=:Ux2uOKOSmMMi1E/M/fYPBB p3ubTe6MEzViXJsj+U5xIaJ556TKhhO10KS/3vOG9bl3rq4xRpCkpuRKnqJ8qS//HzR1ByozC q7bXag0ZAmuYmKSNVkbkwUwEQf/nBWkzwKGH9N74/Vvo3mYuP+VKZO/uGDwcaTzIArz/W2IQ8 bgPbRE2I5bjRbIFapulZBWFlMjvG3kXNNojdvQ8E27s75Y1k023FaUvYeYqkFcXeCQUA8KZrd mF9vlCFb77COWbC3z1NicIka5o705hcbeRxl6mx/SFBw66KpjI/2BxYNXiNSXZKm6flXrMtyv I/TXucVjU8LO3O5WIpejm2bGpIF/PQUQOKKqYmqMLCs2M6oV2xo/OlIEE+0pAoz4xkY5I2kqM 3n9/PDgyTH0iU9VvWgIgHmjzDvf410MZYggDaTOu9Je7qLXF6Gfi8l6Sgx4cCACRMrYx+e1pI 76TwciynBFQBgIBuh6rW61052kLMuTn1MJ1mue7G8o+cBMR6zKwrpDn8RoGbEBpp4WPA7gYJ+ ygtQodBee9C4itDnCDa+SA= X-Spam-Status: No, score=-100.1 required=5.0 tests=BAYES_00, GOOD_FROM_CORINNA_CYGWIN, KAM_DMARC_NONE, KAM_DMARC_STATUS, KAM_NUMSUBJECT, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NEUTRAL, 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: Corinna Vinschen via Cygwin Reply-To: cygwin AT cygwin DOT com Cc: Corinna Vinschen Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" On Apr 21 09:49, Bill Stewart wrote: > On Wed, Apr 21, 2021 at 3:20 AM Corinna Vinschen wrote: > > The problem here is the File System Redirector, > > > > https://docs.microsoft.com/en-us/windows/win32/winprog64/file-system-redirector > > > > This thing is really a problem because it break every, otherwise > > sane assumption. Hmm, bummer. I need some time to think about > > a solution here. > > > > Can you elaborate on what "sane assumptions" get broken? (The redirector is > working as designed, as I understand it?) A sane assumption is for instance, if you cd to foo, that your in foo. That's what the FSR breaks in a thorough way. I. e. on WOW64: $ cd /cygdrive/c/Windows $ ls -1d Sys* SysWOW64 System System32 SystemApps SystemResources So there are two dirs, one called System32, one called SysWOW64. Note how there's *no* such directory called "Sysnative". Still... $ cd System32 works fine. You're just not in System32, but in SysWOW64. Sane? Alternatively: $ cd Sysnative works fine and now you're, oh wonder, in System32. If that's sane, running head first into a wall is, too :) 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