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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=h7NUWTRbXe+Uz8KB
	pjW6JQvNFMFzD21byA+HWxHPRsyvL3guq6DwZxjJvU2SJXQkCFbe3tPddpN10/+M
	86nGAng3Y4OekhFOZ1qQmCI3p2nhpYiggPiB57LpM01cvDmym2kqRX+Qs7+K/1k/
	uvRtYpOcdXDPzB2B2WmRRjEPH88=
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:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; s=default; bh=HdgQBommCtL9s2enlz3SOt
	vTTYg=; b=fVjtrdTXmrhORYvzL2tLq+bLf2ngbIa7cctxTdSJwq+kpFJlxuljbW
	sYXRN6Oyu26TjvwBNDRiIDkdqi/xOBNFuy/pcdI+SYzfdFC1FFMa/uJeldTvhYL4
	K4R9gFdD/IiN952SkaDylLybauXizbir7c/3+E+SwqtallbEs0OVA=
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-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-5.0 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,GIT_PATCH_2,KAM_THEBAT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=UD:ru, letter, HX-Priority:Normal
X-HELO:	forward2j.cmail.yandex.net
Authentication-Results:	smtp3o.mail.yandex.net; dkim=pass header.i=@yandex.ru
X-Yandex-Suid-Status:	1 0,1 0
Date:	Fri, 10 Mar 2017 16:17:23 +0300
From:	Andrey Repin <anrdaemon AT yandex DOT ru>
Reply-To:	cygwin AT cygwin DOT com
Message-ID:	<212519238.20170310161723@yandex.ru>
To:	L A Walsh <cygwin AT tlinx DOT org>, cygwin AT cygwin DOT com
Subject:	Re: Treating Junctions consistently, as "normal dirs" as w/linux "bind"-type mount
In-Reply-To:	<58C1795B.5010809@tlinx.org>
References:	<58A4741E DOT 5020408 AT gmail DOT com> <20170216092611 DOT GE3889 AT calimero DOT vinschen DOT de> <58B0AA58 DOT 30504 AT tlinx DOT org> <20170228214321 DOT GB13542 AT calimero DOT vinschen DOT de> <58C0D744 DOT 2030005 AT tlinx DOT org> <1599023500 DOT 20170309163724 AT yandex DOT ru> <58C1795B DOT 5010809 AT tlinx DOT org>
MIME-Version:	1.0
X-IsSubscribed:	yes

Greetings, L A Walsh!

> Andrey Repin wrote:
>> I would argue against all junctions being treated blindly.
>> The difference with bind mounts in Linux is that in Linux 
>> you don't have the
>> information available within the filesystem itself, and have 
>> no other option,
>> than to treat them as regular directories.
>> Only direct volume junctions cause an issue, and this is what 
>> should be fixed,
>> if possible, not sidetracked with questionable workarounds.
> ----
>         Could you describe the benefits of your proposed solution?

>         You do know that MS originally called junctions "mountpoints",
> right?  So why would cygwin treating them as such be a "questionable 
> workaround"?

How they are called, and how they behave is a two different questions.

>         How would you want to treat them?

Easy way: As symlinks, just like now, unless it's a volume mount point that
can't be normalized to a disk letter.

Preferred way: Fix volume mounts accessibility
 \\?\{UUID} -> /dev/disk/by-uuid/UUID


-- 
With best regards,
Andrey Repin
Friday, March 10, 2017 16:10:57

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

- Raw text -