X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-3.0 required=5.0	tests=BAYES_00,RCVD_NUMERIC_HELO,RP_MATCHES_RCVD,SPF_HELO_PASS
X-Spam-Check-By: sourceware.org
To: cygwin AT cygwin DOT com
From: Andrew DeFaria <Andrew AT DeFaria DOT com>
Subject: Re: Symlinks and sharing a home directory between Windows and Linux
Date: Fri, 16 Dec 2011 08:20:41 -0800
Lines: 23
Message-ID: <jcfr4q$ulp$1@dough.gmane.org>
References: <jcatmu$5d8$1 AT dough DOT gmane DOT org> <4EE90067 DOT 9020109 AT bopp DOT net> <0105D5C1E0353146B1B222348B0411A20A43E78632 AT NIHMLBX02 DOT nih DOT gov> <jcb85e$n8i$1 AT dough DOT gmane DOT org> <jce0v9$eis$1 AT dough DOT gmane DOT org> <4EEABDB8 DOT 4020307 AT cygwin DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111110 Thunderbird/8.0
In-Reply-To: <4EEABDB8.4020307@cygwin.com>
X-Stationery: 0.7.7
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On 12/15/2011 07:40 PM, Larry Hall (Cygwin) wrote:
> I'm having difficulty seeing how what you have described could work 
> unless the consumers of these files are looking for symlinks only, 
> which your example above contradicts.  And both of the ".bashrc" files 
> are registering as plain files, so I think you're right that the file 
> system on which they reside is coming into play, assuming the output 
> above is from Cygwin's 'ls'.  But even if you had ".bashrc" and 
> ".bashrc.lnk" with the former being a UNIX-form of symlink and the 
> latter being the Cygwin one, I'd still expect Cygwin to recognize 
> ".bashrc" first and only go looking for the .lnk version if it 
> couldn't find that.
I would think that Cygwin should see the .lnk version first. No? I guess 
not. I thought it worked that way before.
> The output of strace may convince you of that as well. ;-)  It might 
> actually work as you describe it though if
> you can get Cygwin to think that it can't open the former.  I could 
> see that being the case if the UNIX symlink was created by a user ID 
> Cygwin didn't recognize, for example.
I've backed off to using hardlinks which work on both systems but it 
doesn't work for directories.
-- 
Andrew DeFaria <http://defaria.com>
Accept that some days you're the pigeon, and some days you're the statue.


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