From: Rainer Emrich <rainer-lists@emrich-ebersheim.de>
To: matthew patton <pattonme@yahoo.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: Corinna Vinschen <corinna-cygwin@cygwin.com>
Subject: Re: Cygwin generates syscalls for *.lnk files on filesystems with native symlink support?
Date: Mon, 8 Jan 2024 20:05:49 +0100 [thread overview]
Message-ID: <bd43aaa0-77df-43d6-b339-424a81f9fc32@emrich-ebersheim.de> (raw)
In-Reply-To: <487617694.5562874.1704739459687@mail.yahoo.com>
Am 08.01.2024 um 19:44 schrieb matthew patton via Cygwin:
>> 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
I have CYGWIN=winsymlinks:native
A JUNCTION is created if you try to ln to nonexisting file or directory.
If you ln to an existing directory you get a SYMLINKD and for an
existing file you get SYMLINK, as expected!
Rainer
next prev parent reply other threads:[~2024-01-08 19:05 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 [this message]
2024-01-08 19:17 ` Jeffrey Altman
2024-01-08 19:21 ` Corinna Vinschen
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=bd43aaa0-77df-43d6-b339-424a81f9fc32@emrich-ebersheim.de \
--to=rainer-lists@emrich-ebersheim.de \
--cc=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=pattonme@yahoo.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).