From: "Mingye Wang (Arthur2e5)" <arthur2e5@aosc.xyz>
To: cygwin@cygwin.com
Subject: 2.2.1: NTFS directory symlinks handling
Date: Sat, 22 Aug 2015 00:36:00 -0000 [thread overview]
Message-ID: <55D7C3E0.3020703@aosc.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1503 bytes --]
It is known that cygwin has a naive interpretation for NTFS symlinks, by
translating those paths directly. This works fine with most cases, but
when you link stuffs under `/` to somewhere like `../cygwin/home`, it
simply breaks.
I have a directory tree like this:
|- cygwin/
|- home/
|- Arthur/
|- .gnupg/ (mklink /D .gnupg \Users\Arthur\Appdata\Roaming\gnupg)
|- .ssh/ (mklink /D .ssh \Users\Arthur\.ssh)
|- tmp/
|- 1.txt
|- cygwin64/
|- tmp@ (mklink /D tmp ..\cygwin\tmp)
|- home@ (mklink /D home ..\cygwin\home)
It appears that those `.gnupg` and `.ssh` with an absolute path to the
drive root was interpreted correctly, like
`/cygdrive/c/Users/Arthur/.ssh`, but cygwin64's /tmp and /home breaks,
with the following manner described:
1. Directly interacting with those paths, like attempting a `cd` into
them, cause 'File not found' errors. Running `ls --color` on them gives
a cyan color of it, but doesn't list their contents.
1. `readlink -n /tmp` gives naively translated paths like
`../cygwin/tmp` which I believe what cygwin is using. Adding an extra
link like `ln -s /cygdrive/c/cygwin` fixes this, by making that
`/../cygwin` available.
2. bash also does some startup checking and warns me about '/tmp missing'.
2. Operations like reading the contents of those directories are not
affected. For example, `cd` into `/home/Arthur` and running `cat` on
`/tmp/1.txt`. `ls` works, too.
--
Regards,
Arthur2e5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
next reply other threads:[~2015-08-22 0:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-22 0:36 Mingye Wang (Arthur2e5) [this message]
2015-08-24 13:55 ` cyg Simple
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=55D7C3E0.3020703@aosc.xyz \
--to=arthur2e5@aosc.xyz \
--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).