X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.4.1 sourceware.org 0BDDB3858405
Authentication-Results:	sourceware.org;
	dmarc=fail (p=none dis=none) header.from=nifty.ne.jp
Authentication-Results:	sourceware.org; spf=fail smtp.mailfrom=nifty.ne.jp
DKIM-Filter:	OpenDKIM Filter v2.10.3 conssluserg-04.nifty.com 23U2KHrX005211
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp;
	s=dec2015msa; t=1651285217;
	bh=eedfr8jxYeJwjJwbcmcU6gtNelW4RbG4/ymJyV/y8a8=;
	h=Date:From:To:Cc:Subject:In-Reply-To:References:From;
	b=I2AFLZPtQGNlk4ghMkEoNaruat3dWpJPQJOz6LQPAm3x9AjH4Pz5E39G8vCEdXAFG
	wDO3kBJS8oqCRU8NeyBFzo0JbGNa+gPBYGrNLvQT/qW17Dv+fsOzH66E+4Qf0mqOaJ
	UfjSbLg9qp1r1qYFbEHoQSkjb3APUJy3UbCRebNvOaZhIf5doa18MQNax5WmJtqNaN
	fNuEdFAVGGPBQqMsTlA69rGcaAIrPchEJU7NMUcKHmvyr049Xsbg9g8mZWYMo05h8V
	cWFLBtyjvBgS55hRaA+77x9fc/cgBdzKCJYBCWblwNJV1vKosDw6j4fbbF9tPyGtso
	YEtlJ9RXiPWoA==
X-Nifty-SrcIP:	[119.150.44.95]
Date:	Sat, 30 Apr 2022 11:20:26 +0900
From:	Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
To:	cygwin AT cygwin DOT com
Subject:	Re: bash: cd: /cygdrive/w: Too many levels of symbolic links
Message-Id:	<20220430112026.a45fc5d1502716e4c199d72f@nifty.ne.jp>
In-Reply-To:	<ec4a8f6b-9dc8-405a-a61f-7ab86f93428d@wesbarris.com>
References:	<e895ae39-e128-078d-5758-06804abaccdd AT wesbarris DOT com>
	<20220430080904 DOT 206eada7a267138cc7ff9530 AT nifty DOT ne DOT jp>
	<ec4a8f6b-9dc8-405a-a61f-7ab86f93428d AT wesbarris DOT com>
X-Mailer:	Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version:	1.0
X-Spam-Status:	No, score=-6.1 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE,
	SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version:	SpamAssassin 3.4.4 (2020-01-24) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Cc:	Wes Barris <public1 AT wesbarris DOT com>
Errors-To:	cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

On Fri, 29 Apr 2022 18:27:45 -0500
Wes Barris wrote:
> 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?

We are planning to release cygwin 3.3.5 in which the issue
has been fixed soon after a few ongoing issues will be settled.

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -