DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=wStRSPCng35irfw9XpyGMuRkB2yRYPYvf3OLnlS8c6b
	x7XQS1J0Zt+CzA/vY4G0QKOe6hjxVmmF8/rblvrM0bwE6MJLpbG5E62wpR5ubjAk
	8SImdqNwlBRph2boNOnz7WlpJHxiPf5640QDsc6dcdP/hJyrI4xHLIxfyBfm/LV8
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <58C5AB99.6070906@tlinx.org>
Date: Sun, 12 Mar 2017 13:12:09 -0700
From: L A Walsh <cygwin@tlinx.org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Junctions != Symlinks; Treat Junctions as MS-FS mounts; MS-symlinks are symlinks
References: <58C31431.1020408@tlinx.org> <5110401945.20170311210154@yandex.ru> <58C48EF9.4050106@tlinx.org> <20170312111518.GD3340@calimero.vinschen.de>
In-Reply-To: <20170312111518.GD3340@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Corinna Vinschen wrote:
> On Mar 11 15:57, L A Walsh wrote:
>   
>> 	I'm, talking parallel features and parallel problems.
>> Installing products on Linux or cygwin may check for and
>> complain about symlinks leading to their installation directory.
>>
>> 	The cure in both is to use bind-type mounts and
>> remove any symlink usage in their base path.
>>     
>
> As I wrote (multiple times now?), we can handle dir junctions as
> symlinks or as normal directories.  We can not handle them as mounts or
> bind mounts, unless you do this explicaitly in /etc/fstab or
> /etc/fstab.d/$USER
>   
To a user program, a mountvol looks like a normal directory.
When I talk about a 'bind' mount, I refer to the linux-facility
for mounting an arbitrary directory on a volume on another
directory on linux.  On windows, one uses JUNCTIONs to achive
a similar effect.  In both cases, they look like normal directories.


That said, why not make treating it as a normal
directory dependent on "winsoftlinks:mount" in
the 'CYGWIN' var, with 'winsoftlinks:symlink being
the default (doesn't have to be present in CYGWIN var
to get current behavior). Note, I'm using 'softlink'
as MS uses when talking about JUNCTIONS -- with the new
Vista feature being SYMLINKs.

Thinking about it, when one wants to do backups, the
env-"switch" gives the option of which behavior one gets
(if that's possible/not too hard) -- either the 'normal dir'
look or the current, symlink look.


--
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