This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Symlinks and sharing a home directory between Windows and Linux
- From: Jeremy Bopp <jeremy at bopp dot net>
- To: cygwin at cygwin dot com
- Date: Wed, 14 Dec 2011 14:00:39 -0600
- Subject: Re: Symlinks and sharing a home directory between Windows and Linux
- References: <jcatmu$5d8$1@dough.gmane.org>
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