From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from conssluserg-03.nifty.com (conssluserg-03.nifty.com [210.131.2.82]) by sourceware.org (Postfix) with ESMTPS id 5127D3949F22 for ; Fri, 29 Apr 2022 13:10:48 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 5127D3949F22 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 Received: from Express5800-S70 (ak044095.dynamic.ppp.asahi-net.or.jp [119.150.44.95]) (authenticated) by conssluserg-03.nifty.com with ESMTP id 23TDAIXf000623 for ; Fri, 29 Apr 2022 22:10:18 +0900 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-03.nifty.com 23TDAIXf000623 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nifty.ne.jp; s=dec2015msa; t=1651237818; bh=sKuZ+cOxbw51mtDM7yjTRNUVYWM1b0R0crP4HCx62hk=; h=Date:From:To:Subject:In-Reply-To:References:From; b=Xe2rY5lLow28EQYIrh/tOpMUC0smGEgVsFaUV2a3Bcm/ztG/ygaGFjvnZY1KhpETm n6ucQ5cOJpbQE2akUhTbuQCMJni2c5tSVqtrcFIdPPzqKI4t++gcR6qL7fl2T6HN0A wyGsrF7lnS415YpvUjlEUzE8fVb0INcSBeiQglO/l0CzzZGQyMP1H6W0IgklrrYvR6 3Ggva4TNQknjfkV7XpsFc4SX5xIfsGXdklgW5CLxFa0j8Sanf0rgme9KGOvn+rVNP7 CxeNCO4rC6NYbZ+Ms18mqbQcEWCtsVwT//pHHwWhL4KYFMWjq0LvwnPSSZc8CamC+f xFxOOTuDsU5Mw== X-Nifty-SrcIP: [119.150.44.95] Date: Fri, 29 Apr 2022 22:10:20 +0900 From: Takashi Yano To: cygwin@cygwin.com Subject: Re: Home directory on network drive not accessible in 3.3.4 Message-Id: <20220429221020.4f30ec6c4321e44ef119a954@nifty.ne.jp> In-Reply-To: <8389e966-9712-7011-8012-c0a07d2edc0e@towo.net> References: <8389e966-9712-7011-8012-c0a07d2edc0e@towo.net> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00, BODY_8BITS, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_NUMSUBJECT, 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Apr 2022 13:10:52 -0000 On Fri, 29 Apr 2022 13:59:59 +0200 Thomas Wolff wrote: > I upgraded 3.3.3 → 3.3.4 in a lab environment, where my home directory > is H:\ or /cygdrive/h > > Starting cygwin (cmd/bash or mintty) with some tools from gnuutils (like > ls) in the path gives me this message: > > mkdir: cannot create directory ‘/cygdrive/h’: File exists > /cygdrive/h could not be created. > Setting HOME to /tmp. > > After clearing PATH, then running bash or mintty: > bash: /cygdrive/h/.bashrc: Too many levels of symbolic links > > $ cd /cygdrive/h > -bash: cd: /cygdrive/h: Too many levels of symbolic links > > $ /bin/ls -l /cygdrive > /bin/ls: /cygdrive/h: Too many levels of symbolic links > /bin/ls: /cygdrive/l: Too many levels of symbolic links > total 48 > d---r-x---+ 1 NT SERVICE+TrustedInstaller NT SERVICE+TrustedInstaller 0 > Apr 27 11:01 c > drwx---rwx+ 1 SYSTEM SYSTEM                      0 Mar 23 15:41 d > drwxrwx---  1 Administratoren Domänen-Admins             0 Nov 26 11:40 h > drwxrwxr-x  1 Administratoren Domänen-Admins             0 Dec 17 18:53 l > > $ /bin/mount > //141.64.144.100/Labormaterial/TGI/cygwin64/bin on /usr/bin type ntfs > (binary,auto) > //141.64.144.100/Labormaterial/TGI/cygwin64/lib on /usr/lib type ntfs > (binary,auto) > //141.64.144.100/Labormaterial/TGI/cygwin64 on / type ntfs (binary,auto) > C: on /cygdrive/c type ntfs (binary,posix=0,user,noumount,auto) > D: on /cygdrive/d type ntfs (binary,posix=0,user,noumount,auto) > H: on /cygdrive/h type ntfs (binary,posix=0,user,noumount,auto) > L: on /cygdrive/l type ntfs (binary,posix=0,user,noumount,auto) > > Reverting to cygwin 3.3.3 solves the issue. Maybe related to the other > 3.3.4 problem reported today? This seems to be the issue which was already fixed in git head. https://cygwin.com/pipermail/cygwin-patches/2022q1/011729.html -- Takashi Yano