public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: Home directory on network drive not accessible in 3.3.4
Date: Fri, 29 Apr 2022 22:10:20 +0900	[thread overview]
Message-ID: <20220429221020.4f30ec6c4321e44ef119a954@nifty.ne.jp> (raw)
In-Reply-To: <8389e966-9712-7011-8012-c0a07d2edc0e@towo.net>

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 <takashi.yano@nifty.ne.jp>

      reply	other threads:[~2022-04-29 13:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-29 11:59 Thomas Wolff
2022-04-29 13:10 ` Takashi Yano [this message]

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=20220429221020.4f30ec6c4321e44ef119a954@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --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).