public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: matthew patton <pattonme@yahoo.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>,
	 Jeffrey Altman <jaltman@secure-endpoints.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 19:57:34 +0000 (UTC)	[thread overview]
Message-ID: <1867877038.5579219.1704743854613@mail.yahoo.com> (raw)
In-Reply-To: <2f4c9914-1285-42f0-b841-69335687713a@secure-endpoints.com>

[-- Attachment #1: Type: text/plain, Size: 496 bytes --]

> This breaks many applications such as the java runtime among others.
In any event "unreadable files" is a problem all over the place if I use Cygwin's /usr/bin/ln to create links. That's why I was forced to write a wrapper. Even if 'JUNCTION' is false/misleading as to the root cause, plenty of 'DOS' programs, like the AWS CLI and Golang have major problems with the default behavior.
For a "compatibility" environment to spawn a slew of unusable filesystem artifacts is a MAJOR bug, IMO.

  parent reply	other threads:[~2024-01-08 19:57 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
2024-01-08 19:57               ` matthew patton [this message]
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=1867877038.5579219.1704743854613@mail.yahoo.com \
    --to=pattonme@yahoo.com \
    --cc=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    --cc=jaltman@secure-endpoints.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).