From: Bill Stewart <bstewart@iname.com>
To: cygwin@cygwin.com
Subject: Re: Cannot access system32 directory from 32 bit cygwin after the commit 456c3a46
Date: Wed, 21 Apr 2021 11:57:07 -0600 [thread overview]
Message-ID: <CANV9t=RZ9Z3ZoLPQWtTSTvphp10wy3QAYivo+AZo9-2pJ6m+ZQ@mail.gmail.com> (raw)
In-Reply-To: <YIBXLtdkPnfcfimZ@calimero.vinschen.de>
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.
Bill
next prev parent reply other threads:[~2021-04-21 17:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-21 3:04 Takashi Yano
2021-04-21 8:49 ` Andrey Repin
2021-04-21 9:10 ` Takashi Yano
2021-04-21 9:22 ` Andrey Repin
2021-04-21 10:07 ` Takashi Yano
2021-04-21 9:56 ` Marco Atzeri
2021-04-21 10:09 ` Takashi Yano
2021-04-21 9:19 ` Corinna Vinschen
2021-04-21 14:58 ` Andrey Repin
2021-04-21 15:49 ` Corinna Vinschen
2021-04-21 16:04 ` Brian Inglis
2021-04-22 8:16 ` Csaba Raduly
2021-04-22 8:26 ` Brian Inglis
2021-04-21 15:49 ` Bill Stewart
2021-04-21 16:47 ` Corinna Vinschen
2021-04-21 17:57 ` Bill Stewart [this message]
2021-04-21 19:28 ` Corinna Vinschen
2021-04-21 21:03 ` Bill Stewart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANV9t=RZ9Z3ZoLPQWtTSTvphp10wy3QAYivo+AZo9-2pJ6m+ZQ@mail.gmail.com' \
--to=bstewart@iname.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).