From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Cannot access system32 directory from 32 bit cygwin after the commit 456c3a46
Date: Wed, 21 Apr 2021 19:09:12 +0900 [thread overview]
Message-ID: <20210421190912.27bad7df23365d002f4729ab@nifty.ne.jp> (raw)
In-Reply-To: <b9704ebe-dbb0-26cd-5d64-d7ab3c6faa2f@gmail.com>
On Wed, 21 Apr 2021 11:56:50 +0200
Marco Atzeri wrote:
> On 21.04.2021 10:49, Andrey Repin wrote:
> > Greetings, Takashi Yano!
> >
> >> I noticed the problem that /cygdrive/c/Windows/System32 directory
> >> can be no longer accessed from 32 bit cygwin (WOW64) after the
> >> commit:
> >
> >> Reverting this commit resolves the issue.
> >
> >> 64 bit cygwin does not seem to be affected. Could you please
> >> have a look?
> >
> > How exactly it "can no longer be accessed" ? Is it opening WOW64 System32 or
> > not opening anything at all?
> >
> >
>
> I see no problem on my side
>
> $ uname -svr
> CYGWIN_NT-10.0-WOW 3.2.0(0.340/5/3) 2021-03-29 08:37
>
> $ ls /cygdrive/c/Windows/System32 | wc -l
> 2925
Because your cygwin1.dll is older than the commit:
commit 456c3a46386f38887407603b2c64b7f63a4871c5
Author: Corinna Vinschen <corinna@vinschen.de>
Date: Mon Apr 19 14:49:14 2021 +0200
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2021-04-21 10:09 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 [this message]
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
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=20210421190912.27bad7df23365d002f4729ab@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--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).