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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=ezSzp+KicC1XrPozvV+yglgEDdsmz4hhaqV7P6vnuui
	m/7pWrBif/2aEK/+5UIkiZurBd+SItZlhK4SVeda5RsOiGiUPaD2acQYyXEHt6v2
	Z0duVycAeofgie4KU82D1kKJE/j7izCibOIp4v3LYn5MZP5iYGETOjFORGPVaHco
	=
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:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=3Hcv41tIFb73NABdZZHquivScg0=; b=FCO4eu6uQ1bZOFbDz
	/e1ztGSobRoNOgVLq12TnadON0lOSQNQvDvT3fE0EfQFB4tgeRDt/762FnIsTaDn
	McQKp6Diw351f/8DgN2lQNVYguq8aFqwriSF6tQCNoKFu1M7LrZO5ts8wfMPphkE
	tZIb3POAc+T/PO3AsKI34luPDQ=
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=-0.5 required=5.0 tests=AWL,BAYES_50,RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO: Ishtar.hs.tlinx.org
Message-ID: <5656E3C2.6080405@tlinx.org>
Date: Thu, 26 Nov 2015 02:49:38 -0800
From: Linda Walsh <cygwin AT tlinx DOT org>
User-Agent: Thunderbird
MIME-Version: 1.0
To: David Macek <david DOT macek DOT 0 AT gmail DOT com>,
        "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Another reason to not corrupt winnative symlinks: :currenly, they are linux-CIFS compat.  Cygwin's are not.
References: <564BAA1A DOT 8000703 AT gmail DOT com> <20151118175503 DOT GT6402 AT calimero DOT vinschen DOT de> <56551D13 DOT 10907 AT tlinx DOT org> <5655A3AF DOT 8010601 AT gmail DOT com>
In-Reply-To: <5655A3AF.8010601@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

David Macek wrote:
> Can you describe what purpose does your C:\proc serve? I'm not currently arguing for or against Corinna's proposal, I'm just curious.
> 
---
Notice the date on it... I created it 2-3 years ago...
but it was likely to get some behavior to work the same
with windows utils and linux utils.  I have my cygroot
set to '/' (sorta)...and paths on my linux box and windows 
box often resolve to the same file.  Since the underlying 
NT OS is slash impartial, many pathnames will work w/o conversion.

That's why I tried to get Corrina to support the MS-View of 
MS-junctions being the MS-equiv of linux Mount-points --
She's wiping out linux compatibility by turning them into
the same as 'symlinkd' entries.

I also had both cygwin32 and cygwin64 working on my system
at the same time, with win-applications invoking the 'correct
bit-wise versions and libs by using Ms's 32/64-bit 'system32'
redirect, but having things like tar and rsync ovewrite your
mountpoints on every install and update made it a high maintenance
task.

Basically my login to both machines looks very similar -- same
bash setup.

What was really 'cool' is mounting my win-fs near the root
and having the Windows symlinks ... this is another good reason
not to screw w/things... it will break linux compatibility
even more...   The symlinks on Windows work as unix symlinks
when the share is mounted on a unix dir.  So on linux, I see:
l--------- 1            0 Jul 16  2013 D -> /??/UNC/Ishtar/Documents/
l--------- 1            0 Feb 28  2015 M -> /??/UNC/Bliss/Music/
l--------- 1            0 Feb 28  2015 P -> /??/UNC/Bliss/Pictures/
l--------- 1            0 Mar 28  2013 Share -> /??/UNC/Bliss/Share/
l--------- 1            0 Apr 21  2013 prog64 -> Program Files/
===(among others)...
But those links resolve on linux - I just
created a dir in root named '??'.. etc. and filled
out the structure... so file access on from my linux
machine can resolve seemlessly.  If corrina changes
to a non-compatible symlink format then they won't resolve
as linux symlinks under linux CIFS.





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