public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Issues with Cygwin64 on Windows11
Date: Tue, 2 Aug 2022 09:57:43 -0400	[thread overview]
Message-ID: <d7bf378e-5048-2534-ae3a-81e1f25fe150@cornell.edu> (raw)
In-Reply-To: <YujeH0H3PJOPOGQ3@calimero.vinschen.de>

On 8/2/2022 4:19 AM, Corinna Vinschen wrote:
> On Aug  2 13:12, Takashi Yano wrote:
>> Then, what about the v2 patch attached?
> 
> symlink_wsl is doing the right thing, as Ken points out.

Actually, I was suggesting that symlink_wsl was doing the wrong thing in case 
the user used an uppercase drive letter.  WSL doesn't recognize /mnt/C, so I 
don't think symlink_wsl should convert /cygdrive/C to /mnt/C.

> Therefore, the more effort the code makes to be clever, the higher
> chances are that an incorrect conversion takes place.

Agreed.

>>> I'm tempted to go even further and say that Cygwin shouldn't ever
>>> convert the cygdrive prefix to /mnt, on the grounds that users who
>>> care about WSL interoperability can simply use /mnt as their
>>> cygdrive prefix.  But maybe that ship has sailed.
> 
> In hindsight this might have been a step too far.  I was trying to allow
> interoperability and reduce the number of problems based on different
> drive letter handling.  And, well, this is the first time a user has
> a problem due to that :}
> 
> The ship hasn't sailed entirely.  We can revert this decision for 3.4
> and just keep the /mnt conversion in check_reparse_point_target for
> backward compat.  Or we just fix the problem at hand and otherwise
> keep the code as is...?

The latter seems like the safest solution, rather than risk breaking some other 
use case.

Ken

  reply	other threads:[~2022-08-02 13:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-31  6:11 Dimax
2022-07-31  8:21 ` Takashi Yano
2022-08-01  0:23   ` Takashi Yano
2022-08-02  1:14     ` Ken Brown
2022-08-02  4:12       ` Takashi Yano
2022-08-02  8:19         ` Corinna Vinschen
2022-08-02 13:57           ` Ken Brown [this message]
2022-08-02 14:36             ` Corinna Vinschen
2022-08-02 14:39               ` 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=d7bf378e-5048-2534-ae3a-81e1f25fe150@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).