X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-4.0 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD
X-Spam-Check-By:	sourceware.org
X-IronPortListener:	Outbound_SMTP
X-IronPort-Anti-Spam-Filtered:	true
X-IronPort-Anti-Spam-Result:	An8AAJcC6U6cKEdK/2dsb2JhbABEmmOQR4EFgXIBAQEEEihPAgEIDQscAhAfExcBDQEBBBsah2Cbd5ssiyRjBIgyhDSNe4xb
From:	"Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder AT niaid DOT nih DOT gov>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Date:	Wed, 14 Dec 2011 15:14:29 -0500
Subject:	RE: Symlinks and sharing a home directory between Windows and Linux
Message-ID:	<0105D5C1E0353146B1B222348B0411A20A43E78632@NIHMLBX02.nih.gov>
References:	<jcatmu$5d8$1 AT dough DOT gmane DOT org> <4EE90067 DOT 9020109 AT bopp DOT net>
In-Reply-To:	<4EE90067.9020109@bopp.net>
MIME-Version:	1.0
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
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id pBEKFVTA000450

Jeremy Bopp sent the following at Wednesday, December 14, 2011 3:01 PM
>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?

Might CYGWIN=winsymlinks help?
http://cygwin.com/cygwin-ug-net/using-cygwinenv.html
More:
http://cygwin.com/faq/faq-nochunks.html#faq.using.symlinkstoppedworking
http://cygwin.com/faq/faq-nochunks.html#faq.api.symlinks

Good luck.

- Barry
  Disclaimer: Statements made herein are not made on behalf of NIAID.



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