From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin generates syscalls for *.lnk files on filesystems with native symlink support?
Date: Mon, 8 Jan 2024 20:21:58 +0100 [thread overview]
Message-ID: <ZZxLVnNZJP7jOo7Z@calimero.vinschen.de> (raw)
In-Reply-To: <2f4c9914-1285-42f0-b841-69335687713a@secure-endpoints.com>
On Jan 8 14:17, Jeffrey Altman via Cygwin wrote:
> On 1/8/2024 1:44 PM, matthew patton via Cygwin wrote:
> > > Cygwin does not create symlinks as junctions. No idea where you got that idea.
> > $ echo $CYGWINwinsymlinks:nativestrict
> > $ /usr/bin/ln -s default.GGG6q test1
> > 01/08/2024 01:24 PM <JUNCTION> test1 [...]Type=File
> > $ (unset CYGWIN; /usr/bin/ln -s default.GGG6q test2.nocygwin)
> > 01/08/2024 01:25 PM <JUNCTION> test2.nocygwin [...]Type=File
>
> JUNCTIONS are a type of reparse point tag. Many tools report things as
> JUNCTIONS when they don't know what else to call it because JUNCTIONS were
> the only type of reparse tag commonly used.
> [...]
> As part of this reply I will note that the NTFS symlinks differ from POSIX
> symlinks in significant ways
>
> 1. A pre-existing file system object is required in order to attach a
> reparse tag
> 2. The type of the target must be known when the reparse tag is applied
> to a pre-existing file system object
> 3. The reparse tag may be removed and replaced any number of times
> without deleting the pre-existing object to which it is attached.
> Whereas a POSIX symlink inode target cannot be altered once
> created. The inode must be deleted and replaced.
> 4. The Windows file APIs do not behave as many applications expect them
> to when a symlink reparse tag is present. For example, opening a
> file handle will traverse the reparse tag and open the target but
> the file info api when given the same path will return the
> information belonging to the object on which the reparse tag was
> applied. This breaks many applications such as the java runtime
> among others.
>
> Jeffrey Altman
Thanks, Jeffrey. I couldn't have expressed it so nicely. Very well
summarized.
Corinna
next prev parent reply other threads:[~2024-01-08 19:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 4:23 Cedric Blancher
2023-09-01 10:57 ` Corinna Vinschen
2023-09-26 5:12 ` Cedric Blancher
2023-12-18 12:04 ` Cedric Blancher
2024-01-08 13:56 ` Corinna Vinschen
2024-01-08 17:11 ` matthew patton
2024-01-08 18:11 ` Corinna Vinschen
2024-01-08 18:44 ` matthew patton
2024-01-08 19:05 ` Rainer Emrich
2024-01-08 19:17 ` Jeffrey Altman
2024-01-08 19:21 ` Corinna Vinschen [this message]
2024-01-08 19:57 ` matthew patton
2024-01-08 20:27 ` Brian Inglis
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=ZZxLVnNZJP7jOo7Z@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).