From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19091 invoked by alias); 14 Dec 2011 20:15:25 -0000 Received: (qmail 19075 invoked by uid 22791); 14 Dec 2011 20:15:23 -0000 X-SWARE-Spam-Status: No, hits=-4.0 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from nihxway6out.hub.nih.gov (HELO nihxway6out.hub.nih.gov) (128.231.90.114) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 14 Dec 2011 20:15:09 +0000 X-IronPortListener: Outbound_SMTP X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: An8AAJcC6U6cKEdK/2dsb2JhbABEmmOQR4EFgXIBAQEEEihPAgEIDQscAhAfExcBDQEBBBsah2Cbd5ssiyRjBIgyhDSNe4xb Received: from unknown (HELO NIHHTRC.nih.gov) ([156.40.71.74]) by nihxway6out.hub.nih.gov with ESMTP; 14 Dec 2011 15:15:07 -0500 Received: from NIHMLBX02.nih.gov ([156.40.71.32]) by NIHHTRC.nih.gov ([156.40.71.74]) with mapi; Wed, 14 Dec 2011 15:14:30 -0500 From: "Buchbinder, Barry (NIH/NIAID) [E]" To: "cygwin@cygwin.com" Date: Wed, 14 Dec 2011 20:15:00 -0000 Subject: RE: Symlinks and sharing a home directory between Windows and Linux Message-ID: <0105D5C1E0353146B1B222348B0411A20A43E78632@NIHMLBX02.nih.gov> References: <4EE90067.9020109@bopp.net> In-Reply-To: <4EE90067.9020109@bopp.net> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-12/txt/msg00328.txt.bz2 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 hav= e: >> >> $ 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=3Dwinsymlinks 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