From: Jon Turney <jon.turney@dronecode.org.uk>
To: Cygwin Patches <cygwin-patches@cygwin.com>,
Yoshinao Muramatsu <ysno@ac.auone-net.jp>
Subject: Re: [PATCH 0/3] fix unlink/rename failure in hyper-v container
Date: Fri, 24 Mar 2023 13:20:43 +0000 [thread overview]
Message-ID: <3ca8b41e-41c4-7c34-8912-dc515b3da57e@dronecode.org.uk> (raw)
In-Reply-To: <ZB2Ph+7EkP8evVJo@calimero.vinschen.de>
On 24/03/2023 11:54, Corinna Vinschen wrote:
> On Mar 24 01:40, Yoshinao Muramatsu wrote:
>> On 2023/03/22 2:58, Corinna Vinschen wrote:
>>> I pushed a new Cygwin DLL, test release 3.5.0-0.251.gfe2545e9faaf.
>>> This should do what we want, now. If you can confirm, I'll push
>>> your workaround afterwards.
>>
>> I have tested cygwin-3.5.0-0.251.gfe2545e9faaf.
>> It works fine with bind mounted directory in the hyper-v container.
>
> Thanks, I pushed your patches. We can reevaluate the
> FILE_SUPPORTS_OPEN_BY_FILE_ID handling if Microsoft actually
> changes this in Hyper-V.
>
>> Slightly off-topic, but since I could not use gui to set up cygwin
>> in the container, I am using setup-x86_64.exe with cli.
>> Is there a way to install the cygwin package by specifying
>> the package version from cli?
>
> Uhm... I don't think so. I'm not aware of such a way to define the
> desired package version on the CLI. That would be a nice feature...
'-P cygwin=3.5.0-0.251.gfe2545e9faaf' allegedly works, for a while now.
next prev parent reply other threads:[~2023-03-24 13:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 14:43 YO4
2023-03-17 14:43 ` [PATCH 1/3] fix unlink in container YO4
2023-03-17 14:43 ` [PATCH 2/3] fix rename " YO4
2023-03-17 14:43 ` [PATCH 3/3] log disabling posix semantics YO4
2023-03-17 19:15 ` [PATCH 0/3] fix unlink/rename failure in hyper-v container Corinna Vinschen
2023-03-18 5:29 ` Yoshinao Muramatsu
2023-03-18 10:01 ` Corinna Vinschen
2023-03-20 13:06 ` Yoshinao Muramatsu
2023-03-20 14:51 ` Corinna Vinschen
2023-03-20 14:54 ` Corinna Vinschen
2023-03-20 20:37 ` Corinna Vinschen
2023-03-21 15:32 ` Yoshinao Muramatsu
2023-03-21 17:58 ` Corinna Vinschen
2023-03-23 16:40 ` Yoshinao Muramatsu
2023-03-24 11:54 ` Corinna Vinschen
2023-03-24 13:20 ` Jon Turney [this message]
2023-03-24 13:22 ` Corinna Vinschen
2023-03-24 14:20 ` Jon Turney
2023-03-24 13:48 ` Yoshinao Muramatsu
2023-03-20 11:50 ` [PATCH 0/3] fix unlink/rename failure in hyper-v container(regenerate) Yoshinao Muramatsu
2023-03-20 11:51 ` [PATCH 1/3] fix unlink in container Yoshinao Muramatsu
2023-03-20 11:51 ` [PATCH 2/3] fix rename " Yoshinao Muramatsu
2023-03-20 11:51 ` [PATCH 3/3] log disabling posix semantics Yoshinao Muramatsu
2023-03-20 12:12 ` [PATCH 0/3] fix unlink/rename failure in hyper-v container(regenerate) Corinna Vinschen
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=3ca8b41e-41c4-7c34-8912-dc515b3da57e@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-patches@cygwin.com \
--cc=ysno@ac.auone-net.jp \
/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).