From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Symlinks and sharing a home directory between Windows and Linux
Date: Wed, 14 Dec 2011 20:15:00 -0000 [thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A20A43E78632@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <4EE90067.9020109@bopp.net>
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
next prev parent reply other threads:[~2011-12-14 20:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 19:34 Andrew DeFaria
2011-12-14 20:00 ` Jeremy Bopp
2011-12-14 20:15 ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
2011-12-14 22:32 ` Andrew DeFaria
2011-12-15 23:48 ` Andrew DeFaria
2011-12-16 3:41 ` Larry Hall (Cygwin)
2011-12-16 16:21 ` Andrew DeFaria
2011-12-16 16:47 ` Jon Clugston
2011-12-20 17:44 ` Larry Hall (Cygwin)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0105D5C1E0353146B1B222348B0411A20A43E78632@NIHMLBX02.nih.gov \
--to=bbuchbinder@niaid.nih.gov \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).