From: matthew patton <pattonme@yahoo.com>
To: "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 18:44:19 +0000 (UTC) [thread overview]
Message-ID: <487617694.5562874.1704739459687@mail.yahoo.com> (raw)
In-Reply-To: <ZZw65R578QtNO_4E@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
> 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
# 'ln' is a wrapper function around 'mklink' since Cygwin does the wrong thing.https://github.com/tb3088/shell-environment/blob/ccf7aa161899c2c4ebe2d9e980e674bc726a3ef3/.functions_os.CYGWIN_NT#L10
$ ln default.GGG6q test3.mklinksymbolic link created for test3.mklink <<===>> default.GGG6q01/08/2024 01:25 PM <SYMLINK> test3.mklink [default.GGG6q]Type=.symlink
C:\Users\xxx>type default.GGG6qfoobar
C:\Users\xxx>type test1The file cannot be accessed by the system.
C:\Users\pattonma>type test2.nocygwinThe file cannot be accessed by the system.
C:\Users\xxx>type test3.mklinkfoobar
next prev parent reply other threads:[~2024-01-08 18:44 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 [this message]
2024-01-08 19:05 ` Rainer Emrich
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=487617694.5562874.1704739459687@mail.yahoo.com \
--to=pattonme@yahoo.com \
--cc=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).