public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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 15:03:50 -0600	[thread overview]
Message-ID: <CANV9t=Q=9R49kOW-kVZg5=Mz12Gzzhzh2jxF5E4ZT2DnUQw3KA@mail.gmail.com> (raw)
In-Reply-To: <YIB82EMHEMc0ziW+@calimero.vinschen.de>

On Wed, Apr 21, 2021 at 1:28 PM Corinna Vinschen wrote:

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
>

That would not have worked for backward compatibility reasons.

https://docs.microsoft.com/en-us/previous-versions/technet-magazine/ff955767(v=msdn.10)

The "32" suffix in System32 can be seen as just a label and doesn't
represent the "bitness" of the files within. (As Raymond says, "you should
think of System32 as the somewhat strange name for the 'system DLLs in the
same bitness as the application [in this case, OS] that’s running'
directory").

(You're right - not really the right place to discuss - was just responding
to the evaluative labeling.)

Bill

      reply	other threads:[~2021-04-21 21:04 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
2021-04-21 19:28         ` Corinna Vinschen
2021-04-21 21:03           ` Bill Stewart [this message]

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=Q=9R49kOW-kVZg5=Mz12Gzzhzh2jxF5E4ZT2DnUQw3KA@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).