X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=4.2 required=5.0	tests=AWL,BAYES_05,BOTNET
X-Spam-Check-By: sourceware.org
Message-id: <4EF0C977.2080506@cygwin.com>
Date: Tue, 20 Dec 2011 12:44:23 -0500
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Symlinks and sharing a home directory between Windows and Linux
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>	<jcfr4q$ulp$1 AT dough DOT gmane DOT org> <CAG_2cTnDxK+KW+Ck24wPPRs+yEoq5dSUrZnsC2crGvz5oLR76g AT mail DOT gmail DOT com>
In-reply-to: <CAG_2cTnDxK+KW+Ck24wPPRs+yEoq5dSUrZnsC2crGvz5oLR76g@mail.gmail.com>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
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

On 12/16/2011 11:46 AM, Jon Clugston wrote:
> On Fri, Dec 16, 2011 at 11:20 AM, Andrew DeFaria<Andrew AT defaria DOT com>  wrote:
>> 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.
>
> This would be a performance disaster - forcing a check for 'x.lnk'
> every time the software tried to access file 'x'.  I doubt that it
> worked that way before.

Correct.  It did not work this way for the reason you stated.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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