X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-type
	:content-transfer-encoding:message-id:date:to:cc:subject
	:in-reply-to:references:from; q=dns; s=default; b=QiSfgpyjbl0m3x
	mnLdz7JIZjTGsVAtMt2swIs4jd7PqTDM+Aydt5WRTjfj1O6wCcqPb88KsHU6knTi
	EJEX0wsYv1o5xjJd6OyQygS7BbCNI5hVue56ocM40gxx84/+Qry9bhgl81CchQuQ
	J+EXDYepdlFMVL7qIfzkgPaQ4kxls=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:content-type
	:content-transfer-encoding:message-id:date:to:cc:subject
	:in-reply-to:references:from; s=default; bh=n6dj7HF3kKkOaPCTCBz4
	MRioWUs=; b=w2bGkN48H3HnJkdcOT2YAxvt8uVWhuiL1Am2XHm+0Go/pE6ELaTF
	qFqA+4/oIlH4wwmvhIxxhwKzAe0NhNQLu1JtO4nRTrEa3OpcXDac3qQHszJLoDwf
	hrP3JKrQNoML18j7Hobb44S30qbN4/K8LyQetKqrNncIZJBN/D8U6Ak=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=
X-HELO: p3plsmtpa06-09.prod.phx3.secureserver.net
X-Sender: inbox AT kosowsky DOT org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <24071.55167.544598.384719@consult.pretender>
Date: Sat, 28 Dec 2019 17:30:23 -0500
To: cygwin AT cygwin DOT com
Cc: Jeff <cygwin AT kosowsky DOT org>
Subject: Re: Any downside to using winsymlinks over cygwin-style symlinks?
In-Reply-To: <1501621188.20191227211155@yandex.ru>
References: <24070 DOT 7571 DOT 896562 DOT 93733 AT consult DOT pretender>	<1501621188 DOT 20191227211155 AT yandex DOT ru>
From: cygwin AT kosowsky DOT org
X-IsSubscribed: yes

See comments inline
Andrey Repin wrote at about 21:11:55 +0300 on Friday, December 27, 2019:
 > Greetings, Jeff!
 > 
 > > Based on the documentation and practical use of the Windows-style
 > > symlinks (winsymlinks) vs Cygwin-style symlinks, it seems to me that:
 > > 1. Winsymlinks have the advantage of working as symlinks/shortcuts
 > >    under both Cygwin and Windows Explorer while Cygwin links are
 > >    recognized only in Cygwin
 > 
 > True.
 > 
 > > 2. They both are basically text files with some MAGIC numbers and
 > >    attributes that allow them to be interpreted as symlinks
 > 
 > NOT true.
 > Windows native symlinks are actual FS objects.
 CYGWIN=winsymlinks is the same as CYGWIN=winsymlinks:lnk
 This corresponds to Windows-style links, not native Windows symlinks.
 You are referring to CYGWIN=winsymlinks:native or
CYGWIN=winsymlinks:nativestrict which refers to the true FS object symlinks

> 
 > > So, is there any *disadvantage* to always using Winsymlinks and indeed
 > > converting my old Cygwin-style links to Windows-style?
 > 
 > You can't create native symlinks as a member of Administrators group, even if
 > your account have the needed privilege.

Again note the distinction between winsymlinks and winsymlinks:native
 > 
 > > (Note: I can't use Windows Native symlinks because I don't have admin
 > > privileges on all my machines)
 > 
 > Exactly.
 > 
 > > Finally, where is the best place to set CYGWIN=winsymlinks?
 > > In .bash_profile?
 > 
 > If you can't use them, there's no reason to set this option, if you expect
 > interoperability between Windows and Cygwin.

Again note the distinction between winsymlinks and winsymlinks:native
I was referring winsymlinks (or more pedantically winsymlinks:lnk)

 > With just winsymlinks set, Cygwin will try to create native symlink,
 > but failing that, it will create regular Cygwin symlink.
 > 
 > With winsymlinks:nativestrict set, Cygwin will try to create native symlink
 > and report failure instead of creating Cygwin symlink.
 > 
 > P.S.
 > I'm using winsymlinks:nativestrict personally, but I know implications and
 > well prepared to deal with them.
 > 
 > 
 > -- 
 > With best regards,
 > Andrey Repin
 > Friday, December 27, 2019 21:04:24
 > 
 > Sorry for my terrible english...
 > 

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple