From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 104862 invoked by alias); 26 Nov 2015 10:49:48 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 104846 invoked by uid 89); 26 Nov 2015 10:49:48 -0000 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 Received: from ishtar.tlinx.org (HELO Ishtar.hs.tlinx.org) (173.164.175.65) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 26 Nov 2015 10:49:46 +0000 Received: from [192.168.4.12] (Athenae [192.168.4.12]) by Ishtar.hs.tlinx.org (8.14.9/8.14.4/SuSE Linux 0.8) with ESMTP id tAQAncva002793; Thu, 26 Nov 2015 02:49:41 -0800 Message-ID: <5656E3C2.6080405@tlinx.org> Date: Thu, 26 Nov 2015 11:53:00 -0000 From: Linda Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: David Macek , "cygwin@cygwin.com" Subject: Another reason to not corrupt winnative symlinks: :currenly, they are linux-CIFS compat. Cygwin's are not. References: <564BAA1A.8000703@gmail.com> <20151118175503.GT6402@calimero.vinschen.de> <56551D13.10907@tlinx.org> <5655A3AF.8010601@gmail.com> In-Reply-To: <5655A3AF.8010601@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2015-11/txt/msg00422.txt.bz2 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