X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EF4AC389244D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1619033309;
	bh=fd0Cm2bqsmBeArfu4SKUd4IpuMIaGV/lC8QSX9rsZxo=;
	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=ZNK4GFIMnJGEAOwD1TXQmVmh7tvd1vBmQu5gsvyKbA+1mz6Lh7lGZWXPFo8XSpHd0
	 ZzMg0OZ/MN8Obz708bhsMR6+filWp3wP4fyi/NiZ5BA6qEDElWusSdu0zzVpny+ny4
	 uaoVpBKHAfpQjI8nISaTevmIniCC+tSMI837T2hw=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 5CF6F383802C
Date: Wed, 21 Apr 2021 21:28:24 +0200
To: cygwin AT cygwin DOT com
Subject: Re: Cannot access system32 directory from 32 bit cygwin after the
 commit 456c3a46
Message-ID: <YIB82EMHEMc0ziW+@calimero.vinschen.de>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20210421120457 DOT cd5b6e966288aa62eee1a013 AT nifty DOT ne DOT jp>
 <YH/uPeBvTfxKdRxQ AT calimero DOT vinschen DOT de>
 <CANV9t=Qv2OdnmADgXpk=oVfdchSB+n67tWUruvbiqOrtzh4=Ww AT mail DOT gmail DOT com>
 <YIBXLtdkPnfcfimZ AT calimero DOT vinschen DOT de>
 <CANV9t=RZ9Z3ZoLPQWtTSTvphp10wy3QAYivo+AZo9-2pJ6m+ZQ AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <CANV9t=RZ9Z3ZoLPQWtTSTvphp10wy3QAYivo+AZo9-2pJ6m+ZQ@mail.gmail.com>
X-Provags-ID: V03:K1:JqKrCFF4VOb9zEaIPW3IIopdlIOdz1CyumkfbmLspoAlqBtAMvJ
 EnetmZv+UfEwTFV0QAi87vIR76WyrMXe5IOysG3hf/y44ECr4hc88pyDK9/MJ6fw/jcoH0X
 Dt029FFji+QwFuQjrU8QMPOFkKMYPlEejQ4q2OvdpF00LEk8g0GuvmCYrgtO0l0X6pJtODC
 R1KqsWMu4cBBkqY4lwEXA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:7fTfi184COQ=:YKtyt7L23cYA5KykHwbhtt
 QQukOd8pZZTjlAVKBMXJocf6qvjzMpxSw9jwBmxx/O2YY7sl0VlLCwGFbY/+EUe+gjP5+D4lM
 ONjhcbS/Z0xPLyJuDVQB2DKxWWlCGjTZVqNLqzb/zw3GTp66NgYFD7RYaBWV0Gb22ZLtJAT/1
 QhCzMUNyy9muqgu++QulHjhnxjNrNoSRxXrqExmnLU8SSMMx7GZOY0Fy2nXnSsRp0xIwaUnzj
 11lHretdLOlr9cEZZCGC79AnIYuIcsixzEwSBjOoJehT8n9GSJqKlfJ4d6ge5XwtwfOmDCXar
 XMps9QX/OFtJw49ywvdkMCgY1TiIPCMnEf26jO6PpugbCTHfTgJJLuUSCoUlvlO1aO1LBucU0
 ySt59eq6RTaa9S16iGjbNtUHf+o7AXkHhmXS5NXQP1ru2MDvS+ZigwwrLqFhrhlK5xd9MPUKP
 w+29CMtMmisQRt7DJeAQ/WCyYl8M2w6gC+Ve5AXD9mmR+CWNf/B6UB0Sk4KXCaKYSdIjxcY1+
 K/rnb3MczaWNz+GTTWlf7A=
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 <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Corinna Vinschen via Cygwin <cygwin AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
Cc: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces AT cygwin DOT com>

On Apr 21 11:57, Bill Stewart wrote:
> On Wed, Apr 21, 2021 at 10:47 AM Corinna Vinschenwrote:
> 
> 
> > 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.
> >
> 
> This is, of course, completely expected (notwithstanding the confusion
> caused by the "bitness" names being opposite of what some expect).
> 
> 
> > Note how there's *no* such directory called "Sysnative".  Still...
> >
> >   $ cd System32
> >
> > works fine.  You're just not in System32, but in SysWOW64.  Sane?
> >
> 
> This is completely sensible and expected, as the entire point of the WoW
> emulator is to emulate 32-bit Windows.
> 
> 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 :)
> >
> 
> "Sysnative" isn't an actual file system directory, as noted, but an "alias"
> (for lack of a better word) that allows, from a Wow64 process, to refer to
> the real 64-bit system directory. You can use the name "Sysnative" if you
> are certain you really want to refer to the 64-bit system directory.
> 
> This all seems like a pretty straightforward and sensible approach, IMO.

This is not the right place to discuss this in detail, but to me, a
straightforward and sensible approach would have been to give the 64
bit system dir another name right from the start:

  C:\Windows\System64


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