From: matthew patton <pattonme@yahoo.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: Brian Inglis <brian.inglis@shaw.ca>
Subject: Re: Cygwin tool to differ junctions from soft links?
Date: Fri, 17 Nov 2023 18:44:18 +0000 (UTC) [thread overview]
Message-ID: <2073268580.2731955.1700246658555@mail.yahoo.com> (raw)
In-Reply-To: <fa1a4430-5da1-4f2b-8b6e-873a8c036d40@Shaw.ca>
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
>> Cygwin never creates Windows Directory or Filesystem Junction reparse points,
>> and by default it uses its own version of Unix path symlink files, preceded by
>> a flag ("magic cookie") value, and with system attribute, to allow
>> compatibility with FAT file system limitations, or else NFS symlinks on NFS
>> filesystems.
>> CYGWIN env var settings allow creation of Windows shortcuts and symbolic link
>> reparse points instead of its default (equivalent to winsymlinks:sys), when
>> supported by the file system and Windows release:
>> https://cygwin.com/cygwin-ug-net/using-cygwinenv.html
>> https://cygwin.com/cygwin-ug-net/using.html#pathnames-symlinks
That ^^^ hasn't been true for how many years now? That was the OLD, deprecated mechanism which hasn't seen the light of day since what, WIndows 7 or 10?
13:36 45 $ unset CYGWIN; /bin/ln -s README.md test-link13:37 46 $ cmd /c dir /a: test-link
Volume in drive C is Windows
Directory of C:\Users\pattonma
11/17/2023 01:37 PM <JUNCTION> test-link [...] 1 File(s) 0 bytes 0 Dir(s) 241,024,512,000 bytes free
My environment is shared between Win10, Cygwin, and WSL and Dropbox for a bunch of targets of symlinks. Some 'DOS' tools, specifically AWS CLI can't follow Junctions so I had to take matters into my own hands.
prev parent reply other threads:[~2023-11-17 18:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 9:14 Martin Wege
2023-11-16 7:29 ` Martin Wege
2023-11-17 1:59 ` Doug Henderson
2023-11-16 8:47 ` Andrey Repin
2023-11-16 18:55 ` matthew patton
2023-11-16 20:30 ` Brian Inglis
2023-11-17 5:54 ` Thomas Wolff
2023-11-17 12:06 ` Corinna Vinschen
2023-11-17 14:56 ` Brian Inglis
2023-11-17 18:44 ` matthew patton [this message]
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=2073268580.2731955.1700246658555@mail.yahoo.com \
--to=pattonme@yahoo.com \
--cc=brian.inglis@shaw.ca \
--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).