From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: WSL symbolic links
Date: Fri, 27 Mar 2020 19:53:40 +0100 [thread overview]
Message-ID: <20200327185340.GN3261@calimero.vinschen.de> (raw)
In-Reply-To: <bc0451f2-a1a7-3044-5b0a-119b91d19f9f@SystematicSw.ab.ca>
[-- Attachment #1: Type: text/plain, Size: 2112 bytes --]
On Mar 27 11:58, Brian Inglis wrote:
> On 2020-03-26 14:05, Corinna Vinschen wrote:
> > On Mar 26 13:12, Brian Inglis wrote:
> >> On 2020-03-26 05:00, Corinna Vinschen wrote:
> >>> On Mar 26 10:00, Thomas Wolff wrote:
> >>>> A symbolic link created with WSL is neither interpreted in cygwin nor can it
> >>>> be deleted:
> >>>>> touch file
> >>>>> wsl ln -s file link
> >>>>> wsl ls -l link
> >>>> lrwxrwxrwx 1 towo towo 1 Mar 26 08:56 link -> file
> >>>>> ls -l link
> >>>> -rw-r----- 1 Unknown+User Unknown+Group 0 Mar 26 00:00 link
> >>> What kind of file are they in the real world? Reparse points? If so,
> >>> what content do they have? I attached a Q&D source from my vault
> >>> of old test apps to check on reparse point content. Please compile with
> >>> gcc -g ../src/rd-reparse.c -o rd-reparse -lntdll
> >>> It takes a single native NT path as parameter, kind of like this:
> >>> ./rd-reparse '\??\C:\cygwin64\home\corinna\link'
> >> They should be WSL or Windows mklink (soft) links, and the reason why mklink was
> >> allowed unelevated in Windows 10 with Developer mode.
> >> In an *elevated* shell:
> >> $ ls -dln u
> >> -rw-r----- 1 4294967295 4294967295 0 Nov 9 06:09 u
> > ^^^^^^^^^^^^^^^^^^^^^
> > This is unknown user, unknown group, which means, the Windows
> > function LookupAccountSid() probably returned a domain name which
> > is unknown (neither account domain, nor primary, nor trusted domain).
> >
> > An strace of `ls -l u' may be helpful...
>
> Attached with startup environment, locale, and message setup cut (reduced by
> 100KB), and rest sanitized as below. Could DM/PM original on request.
Thanks! This should already be fixed in the latest developer snapshot
after I was finally able to install WSL myself. See my reply to Thomas
in https://sourceware.org/pipermail/cygwin/2020-March/244211.html
All the effects are a result of not opening the reparse point as reparse
point, as weird as it sounds at first :)
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-03-27 18:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 9:00 Thomas Wolff
2020-03-26 11:00 ` Corinna Vinschen
2020-03-26 16:15 ` Thomas Wolff
2020-03-26 19:12 ` Brian Inglis
2020-03-26 19:56 ` Corinna Vinschen
2020-03-26 23:52 ` Thomas Wolff
2020-03-27 5:46 ` ASSI
2020-03-27 11:21 ` Corinna Vinschen
2020-03-27 12:24 ` Thomas Wolff
2020-03-27 13:01 ` Corinna Vinschen
2020-03-27 14:43 ` Thomas Wolff
2020-03-26 20:05 ` Corinna Vinschen
2020-03-27 17:58 ` Brian Inglis
2020-03-27 18:53 ` Corinna Vinschen [this message]
2020-03-28 3:32 ` Brian Inglis
2020-03-28 10:31 ` Henry S. Thompson
2020-03-28 11:30 ` Thomas Wolff
2020-03-28 11:59 ` Andrey Repin
2020-03-28 20:45 ` Brian Inglis
2020-03-29 11:52 ` Andrey Repin
2020-03-30 8:46 ` Corinna Vinschen
2020-04-04 14:32 ` Denis Excoffier
2020-04-05 15:22 ` 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=20200327185340.GN3261@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).