From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Change in logical link behaviour
Date: Mon, 02 Mar 2020 16:49:00 -0000 [thread overview]
Message-ID: <20200302164851.GS4045@calimero.vinschen.de> (raw)
In-Reply-To: <30792264-c452-7ea2-c83f-f368322387ea@emrich-ebersheim.de>
[-- Attachment #1: Type: text/plain, Size: 3347 bytes --]
On Feb 29 14:10, Rainer Emrich wrote:
> I try to reliably determine if native Windows symlink are working for a
> current cygwin environment in a shell script.
>
> Therefor I used a powershell snipped:
>
> mkdir asdfgh
> ln -s asdfgh/ asdfgh-1
> powershell "& {Get-Item -Path asdfgh-1 | Select-Object}"
>
> On cygwin 3.0.7 the output is as follows:
>
>
> Directory: D:\cygwin\home\rainer\temp
>
>
> Mode LastWriteTime Length Name
> ---- ------------- ------ ----
> d----l 29.02.2020 13:58 asdfgh-1
>
> On cygwin 3.1.4 I get:
>
>
> Directory: D:\cygwin\home\rainer\temp
>
>
> Mode LastWriteTime Length Name
> ---- ------------- ------ ----
> d---- 29.02.2020 13:58 asdfgh-1
>
> So now there is no indication that this is a link. Is this new behaviour
> intended or a bug?
>
> I did not try on Windows 10, I'm still on windows 7.
>
> Rainer
>
I can't reproduce this behaviour. Keep in mind that, by default, you
*have to* run in an elevated shell to be able to create native NTFS
symlinks, *and* you *have to* set the environment variable CYGWIN(*) to
contain "winsymlinks:native" or "winsymlinks:nativestrict". The latter
is nice for testing, it refuses to fall back silently to the default
Cygwin-only symlinks but fails instead if it can't create a native
NTFS symlink.
So, on Windows 7 in an elevated shell:
# id -G | grep -Eq '\<544\>' && echo elevated || echo non-elevated
elevated
# uname -a
CYGWIN_NT-6.1 vmbert764 3.1.4(0.340/5/3) 2020-02-19 08:49 x86_64 Cygwin
# mkdir qwe
# cd qwe
# export CYGWIN="winsymlinks:nativestrict"
# touch foo
# ln -s foo bar
# cmd /c dir /a
Volume in drive C has no label.
Volume Serial Number is A8E0-A24E
Directory of C:\cygwin64\home\corinna\qwe
2020-03-02 17:31 <DIR> .
2020-03-02 17:31 <DIR> ..
2020-03-02 17:31 <SYMLINK> bar [foo]
2020-03-02 17:31 0 foo
2 File(s) 0 bytes
2 Dir(s) 7.907.352.576 bytes free
In a non-elevated shell:
$ id -G | grep -Eq '\<544\>' && echo elevated || echo non-elevated
non-elevated
$ uname -r
CYGWIN_NT-6.1 vmbert764 3.1.4(0.340/5/3) 2020-02-19 08:49 x86_64 Cygwin
$ cd qwe
$ export CYGWIN="winsymlinks:nativestrict"
$ rm bar
$ ln -s foo bar
ln: failed to create symbolic link 'bar': Operation not permitted
$ export CYGWIN="winsymlinks:native" # !!!
$ ln -s foo bar
$ cmd /c dir /a
Volume in drive C has no label.
Volume Serial Number is A8E0-A24E
Directory of C:\cygwin64\home\corinna\qwe
2020-03-02 17:31 <DIR> .
2020-03-02 17:31 <DIR> ..
2020-03-02 17:38 20 bar
2020-03-02 17:31 0 foo
2 File(s) 20 bytes
2 Dir(s) 7.907.352.576 bytes free
The symlink created last is a Cygwin-only symlink (special file
with SYSTEM attribute), not a native symlink.
Corinna
(*) https://cygwin.com/cygwin-ug-net/using-cygwinenv.html
(*) https://cygwin.com/cygwin-ug-net/using.html#pathnames-symlinks
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-03-02 16:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 13:11 Rainer Emrich
2020-03-01 2:05 ` Andrey Repin
2020-03-01 17:01 ` Rainer Emrich
2020-03-02 16:49 ` Corinna Vinschen [this message]
2020-03-03 13:17 ` Rainer Emrich
2020-03-03 13:39 ` Rainer Emrich
2020-03-03 14:19 ` Corinna Vinschen
2020-03-03 14:27 ` Rainer Emrich
2020-03-03 14:31 ` Rainer Emrich
2020-03-03 16:05 ` Corinna Vinschen
2020-03-03 16:32 ` Corinna Vinschen
2020-03-03 16:41 ` Rainer Emrich
2020-03-03 16:46 ` Rainer Emrich
2020-03-03 17:34 ` Corinna Vinschen
2020-03-03 21:43 ` Rainer Emrich
2020-03-04 19:45 ` Andrey Repin
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=20200302164851.GS4045@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).