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 055293858C27
Authentication-Results:	sourceware.org;
	dmarc=none (p=none dis=none) header.from=kosowsky.org
Authentication-Results:	sourceware.org; spf=pass smtp.mailfrom=kosowsky.org
X-CMAE-Analysis:	v=2.4 cv=LNaj/La9 c=1 sm=1 tr=0 ts=61d0dd3f
	a=BYuR5sdBHlGgEYWvfiqr5Q==:117 a=BYuR5sdBHlGgEYWvfiqr5Q==:17
	a=kj9zAlcOel0A:10 a=DghFqjY3_ZEA:10 a=Vn20bfqVWedANTjQ-AIA:9 a=CjuIK1q_8ugA:10
X-SECURESERVER-ACCT:	inbox AT kosowsky DOT org
X-Spam-Checker-Version:	SpamAssassin 3.4.4 (2020-01-24) on
	server2.sourceware.org
X-Spam-Status:	No, score=0.2 required=5.0 tests=BAYES_00, FROM_BLANK_NAME,
	KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL,
	SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4
MIME-Version:	1.0
Message-ID:	<25040.56638.44943.834427@consult.pretender>
Date:	Sat, 1 Jan 2022 18:01:18 -0500
To:	cygwin AT cygwin DOT com
Subject:	Follow-up to: vboxsharedfs - Too many levels of symbolic links
X-Mailer:	VM 8.2.0b under 25.2.2 (x86_64-pc-linux-gnu)
From:	"" <cygwin AT kosowsky DOT org>
X-Virus-Scanned:	ClamAV using ClamSMTP
X-CMAE-Envelope:	MS4xfGcNfQXLORVygiaPl3XeMf3V0SyGPTZZFqsqsClu3Dneyu5SbM1iXf5SSbk4hAM/ORIRTlTlEXAo7sPzYolGeDldqmUSq9W7OX5vUXGBAEPVCmzRfE4q
	+XKsrwCOrdxnQMwyzRYRhRtBdQ0j0Uoi2lu3wL8bGNKzHFtk8Cz7HdrU/AoFTgh4/4n1xk0zNJ2RnckBwlZyyLpo+D+ztJ1RN8o=
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-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>
Sender:	"Cygwin" <cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com>

Hi,
About a month ago, a thread with the above title mentioned that a
patch to the problem was submitted.

I am encountering the same problem on my Cygwin/Win10/Vbox 6.1.30
installation.

Any idea when that patch will be pushed to production?
Or barring that, is there a test version that I could download
somewhere as this bug is somewhat limiting for me at this point...

-- 
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 -