From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10197 invoked by alias); 14 Dec 2011 20:00:59 -0000 Received: (qmail 10187 invoked by uid 22791); 14 Dec 2011 20:00:58 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mail32.mailforbusiness.com (HELO mail32.mailforbusiness.com) (64.106.209.59) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 14 Dec 2011 20:00:45 +0000 Received: from mail32.mailforbusiness.com (localhost [127.0.0.1]) by mail32.mailforbusiness.com (Postfix) with ESMTP id D65F499883 for ; Wed, 14 Dec 2011 15:00:43 -0500 (EST) Received: from [10.10.50.127] (67-198-47-100.static.grandenetworks.net [67.198.47.100]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeremy@bopp.net) by mail32.mailforbusiness.com (Postfix) with ESMTPSA id 2A83C99882 for ; Wed, 14 Dec 2011 15:00:43 -0500 (EST) Message-ID: <4EE90067.9020109@bopp.net> Date: Wed, 14 Dec 2011 20:00:00 -0000 From: Jeremy Bopp User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111124 Thunderbird/8.0 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Symlinks and sharing a home directory between Windows and Linux References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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/msg00327.txt.bz2 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