From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Issues with Cygwin64 on Windows11
Date: Mon, 1 Aug 2022 21:14:52 -0400 [thread overview]
Message-ID: <c9feffc3-a4e2-6419-2e80-10322f70cf49@cornell.edu> (raw)
In-Reply-To: <20220801092349.860472b4da6f3a781eb3ffc4@nifty.ne.jp>
On 7/31/2022 8:23 PM, Takashi Yano wrote:
> On Sun, 31 Jul 2022 17:21:32 +0900
> Takashi Yano wrote:
>> On Sun, 31 Jul 2022 09:11:17 +0300
>> Dimax wrote:
>>> Hello.
>>> I've never had much luck with Cygwin64 and used the 32 bit version before.
>>> Today I have no choice and I've installed Cyg64 on my new Win11 PC.
>>>
>>> Here is the first major issue I faced. I can not create symbolic links:
>>>
>>> Alex@Alexo ~
>>> $ ls /cygdrive/C/XOL/
>>>
>>> Alex@Alexo ~
>>> $ ln -s /cygdrive/C/XOL/ work
>>>
>>> Alex@Alexo ~
>>> $ ls -all work
>>> lrwxrwxrwx 1 Alex None 11 Jul 31 09:09 work -> /mnt/C/XOL/
>>>
>>> Alex@Alexo ~
>>> $ cd ~/work/
>>> -bash: cd: /home/Alex/work/: No such file or directory
>>>
>>> The link is created but I can not use it.
>>> The only thing that I did not standard was to call installation folder
>>> C:\Cygwin instead of default C:\Cygwin64
>>>
>>> Any help would be highly appreciated.
>>
>> Thanks for the report. This seems to happen only when
>> the drive letter is uppercase.
>>
>> ln -s /cygdrive/c/XOL/ work
>> works.
>>
>> Anyway, I think this is a problem of cygwin1.dll.
>>
>> This
>> work -> /mnt/C/XOL/
>> should be
>> work -> /cygdrive/C/XOL/
>> shouldn't it?
>>
>> It guess this is a bug in the code added for WSL
>> compatibility.
>
> I found the patch attached solves the issue.
>
> Corinna, WDYT?
I'm not Corinna, but replacing oldpath by normpath doesn't seem like the right
thing to do at the time of symlink creation. If I create a symlink under
Cygwin, I expect the target to be used under Cygwin exactly as I enter it. The
internal replacement of the cygdrive prefix by /mnt for WSL compatibility is
fine, as long as I never see it except under WSL. But since WSL doesn't
recognize /mnt/<uppercase drive letter>, I don't think Cygwin should convert
/<cygdrive prefix>/<uppercase drive letter>. Users who want WSL
interoperability just have to use lowercase drive letters.
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.
Ken
next prev parent reply other threads:[~2022-08-02 1:14 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 [this message]
2022-08-02 4:12 ` Takashi Yano
2022-08-02 8:19 ` Corinna Vinschen
2022-08-02 13:57 ` Ken Brown
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=c9feffc3-a4e2-6419-2e80-10322f70cf49@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).