From: clayne@anodized.com
To: cygwin@cygwin.com
Subject: Re: native symlinks and non-existent targets
Date: Wed, 24 Apr 2024 22:36:34 +0000 [thread overview]
Message-ID: <ZimJchxllNm8P96S@mercury.signalpunk.com> (raw)
In-Reply-To: <ZimDqKx1R13FdV2q@mercury.signalpunk.com>
On Wed, Apr 24, 2024 at 10:11:52PM +0000, Christopher Layne via Cygwin wrote:
> Based on past threads I've read I believe the issue is actually with
> windows not allowing a symlink to be created with a non-existent target,
> but I do know windows does not care if you break a link after the fact.
Actually, after referring to some microsoft documentation, is this even
true?
https://learn.microsoft.com/en-us/windows/win32/fileio/symbolic-link-programming-considerations
---
Programming Considerations (Local File Systems)
Article 03/03/2021 5 contributors
Keep the following programming considerations in mind when working with symbolic links:
* Symbolic links can point to a non-existent target.
* When creating a symbolic link, the operating system does not check to see if the target exists.
* If an application tries to open a non-existent target, ERROR_FILE_NOT_FOUND is returned.
* Symbolic links are reparse points. For more information, see Determining Whether a Directory Is a Mounted Folder.
* There is a maximum of 63 reparse points (and therefore symbolic links) allowed in a particular path.
(Windows Server 2003 and Windows XP: There is a limit of 31 reparse points on any given path.)
---
If it isn't true then this seems trivial to fix.
-cl
next prev parent reply other threads:[~2024-04-24 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 22:11 clayne
2024-04-24 22:36 ` clayne [this message]
2024-04-25 13:15 ` Jon Turney
2024-04-29 20:11 ` Csaba Ráduly
2024-04-29 21:15 ` Lee
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=ZimJchxllNm8P96S@mercury.signalpunk.com \
--to=clayne@anodized.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).