From: Wes Barris <public1@wesbarris.com>
To: cygwin@cygwin.com
Subject: Re: bash: cd: /cygdrive/w: Too many levels of symbolic links
Date: Fri, 29 Apr 2022 18:27:45 -0500 [thread overview]
Message-ID: <ec4a8f6b-9dc8-405a-a61f-7ab86f93428d@wesbarris.com> (raw)
In-Reply-To: <20220430080904.206eada7a267138cc7ff9530@nifty.ne.jp>
On 4/29/2022 6:09 PM, Takashi Yano wrote:
> On Fri, 29 Apr 2022 14:21:01 -0500
> Wes Barris wrote:
>> For the past couple of months the latest versions of cygwin produce this error
>> when attempting to reference a network drive. There have been a couple of other
>> threads reporting this and talk about patches. Is there a fix coming for this
>> in the production version of cygwin?
>>
>> $ cd /cygdrive/w
>> bash: cd: /cygdrive/w: Too many levels of symbolic links
>> $ mount
>> C:/cygwin64/bin on /usr/bin type ntfs (binary,auto)
>> C:/cygwin64/lib on /usr/lib type ntfs (binary,auto)
>> C:/cygwin64 on / type ntfs (binary,auto)
>> C: on /cygdrive/c type ntfs (binary,noacl,posix=0,user,noumount,auto)
>> D: on /cygdrive/d type ntfs (binary,noacl,posix=0,user,noumount,auto)
>> M: on /cygdrive/m type ntfs (binary,noacl,posix=0,user,noumount,auto)
>> P: on /cygdrive/p type ntfs (binary,noacl,posix=0,user,noumount,auto)
>> S: on /cygdrive/s type ntfs (binary,noacl,posix=0,user,noumount,auto)
>> V: on /cygdrive/v type ntfs (binary,noacl,posix=0,user,noumount,auto)
>> W: on /cygdrive/w type ntfs (binary,noacl,posix=0,user,noumount,auto)
>
> https://cygwin.com/pipermail/cygwin/2022-April/251332.html
>
Thanks. Yes, that post describes what is happening to me. Is there a fix
coming for this?
--
Wes Barris
--
This email has been checked for viruses by AVG.
https://www.avg.com
next prev parent reply other threads:[~2022-04-29 23:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 19:21 Wes Barris
2022-04-29 23:09 ` Takashi Yano
2022-04-29 23:27 ` Wes Barris [this message]
2022-04-30 2:20 ` Takashi Yano
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=ec4a8f6b-9dc8-405a-a61f-7ab86f93428d@wesbarris.com \
--to=public1@wesbarris.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).