X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-4.4 required=5.0 tests=BAYES_00,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:	Symlinks and sharing a home directory between Windows and Linux
Date:	Wed, 14 Dec 2011 11:33:46 -0800
Lines:	27
Message-ID:	<jcatmu$5d8$1@dough.gmane.org>
Mime-Version:	1.0
User-Agent:	Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
X-Stationery:	0.7.7
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

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?


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

- Raw text -