public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: BRISLANE Mark <mark.brislane@partners.axa>, cygwin@cygwin.com
Subject: Re: Cygwin 3.3.4 - cmd to symlinked path doesn't work
Date: Tue, 1 Feb 2022 15:47:25 +0300	[thread overview]
Message-ID: <1157721958.20220201154725@yandex.ru> (raw)
In-Reply-To: <VI1PR04MB41575EBC7E202ACC1249553186269@VI1PR04MB4157.eurprd04.prod.outlook.com>

Greetings, BRISLANE Mark!

> We had this issue in 3.3.3 and is down as being fixed in 3.3.4-2 but
> perhaps our scenario is slightly different because it's still happening.
> SERVER1 has a folder on D: called folder 1, which is a symlink to
> "\\server2\share\folder1" - created with mklink /D folder1 \\server2\share\folder1

> DOMAIN+Administrator@SERVER1 /cygdrive/d
> $ ls -l
> total 3
> drwxr-x---+ 1 Administrators SERVER1+None     0 Jan 28 11:03 '$RECYCLE.BIN'
> d---rwx---+ 1 Administrators SYSTEM                0 Jan 25 23:07 'System Volume Information'
> lrwxrwxrwx  1 Administrators DOMAIN+Domain Users   32 Nov  9 10:52  folder1 -> //server2/share/folder1

> DOMAIN+Administrator@SERVER1 /cygdrive/d
> $ cd folder1

> DOMAIN+Administrator@SERVER1 /cygdrive/d/folder1
> $ cmd
> '\\server2\share\folder1'
> CMD.EXE was started with the above path as the current directory.
> UNC paths are not supported.  Defaulting to Windows directory.
> Microsoft Windows [Version 10.0.14393]
> (c) 2016 Microsoft Corporation. All rights reserved.

> C:\Windows>

> This used to work in older versions of Cygwin.

The interesting part is that the behavior is dependent on sequence of events.

`mintty bash -i` in a directory:

> $ pwd
> /cygdrive/d/cygwin
> $ cmd
> Microsoft Windows [Version 6.1.7601]
> Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
>
> D:\cygwin> exit
>
> $ cd $( pwd )
> $ pwd
> /cygdrive/d/cygwin
> $ cmd
> Microsoft Windows [Version 6.1.7601]
> Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
>
> \\DAEMON1.DARKDRAGON.LAN\arc\cygwin>


-- 
With best regards,
Andrey Repin
Tuesday, February 1, 2022 15:28:28

Sorry for my terrible english...


  reply	other threads:[~2022-02-01 12:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-01 11:46 BRISLANE Mark
2022-02-01 12:47 ` Andrey Repin [this message]
2022-02-01 14:03   ` [EXTERNAL] " BRISLANE Mark
2022-02-01 14:34   ` Corinna Vinschen
2022-02-03 10:56     ` Andrey Repin
2022-02-03 11:34       ` Corinna Vinschen

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=1157721958.20220201154725@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=mark.brislane@partners.axa \
    /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).