X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.5 required=5.0	tests=AWL,BAYES_00
X-Spam-Check-By: sourceware.org
Message-ID: <4EE90067.9020109@bopp.net>
Date: Wed, 14 Dec 2011 14:00:39 -0600
From: Jeremy Bopp <jeremy AT bopp DOT net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111124 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>
In-Reply-To: <jcatmu$5d8$1@dough.gmane.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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/14/2011 01:33 PM, Andrew DeFaria wrote:
> I like having only one home directory. It's extremely convenient to have
> the same settings and the like both when on Cygwin and when on Linux.
> 
> Often home directories are on NAS's and the like and served out via smb.
> 
> Somewhere along the line Cygwin's symlink implementation changed again.
> It used to be that symlinks ended in .lnk, which was sort of a pain but
> workable. One nice thing is that they didn't clash with Linux symlinks.
> A Cygwin symlink is not the same as a Linux symlink and so you could have:
> 
> $ ln -s a_file.txt link1 # in Cygwin
> $ ln -s a_file.txt link1 # in Linux
> 
> and you'd end up having a symlink with the same name, link1, pointing to
> the same file from either Cygwin or Linux. This is because the Linux
> symlink is named just "link1" and the Cygwin symlink is named "link1.txt".
> 
> But now Cygwin names its symlink "link1". When you then log into Linux
> and try to access that link it doesn't work.
> 
> Where this is happening for me is that I put all of my rc files under
> ~/.rc and then I symlink them to ~ as appropriate. So, for example I
> have a ~/.rc/inputrc. I then symlink them to ~/.inputrc. Under the old
> scenario I'd get a ~/.inputrc.lnk for Cygwin and a ~/.inputrc on Linux.
> Under the new scenario I get a clash.
> 
> Is there any way around this?

Would a hard link work instead?

-Jeremy

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