From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6705 invoked by alias); 16 Dec 2011 16:47:02 -0000 Received: (qmail 6689 invoked by uid 22791); 16 Dec 2011 16:47:00 -0000 X-SWARE-Spam-Status: No, hits=-0.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM X-Spam-Check-By: sourceware.org Received: from mail-fx0-f43.google.com (HELO mail-fx0-f43.google.com) (209.85.161.43) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 16 Dec 2011 16:46:47 +0000 Received: by faap21 with SMTP id p21so3841353faa.2 for ; Fri, 16 Dec 2011 08:46:45 -0800 (PST) MIME-Version: 1.0 Received: by 10.180.4.42 with SMTP id h10mr13470468wih.22.1324054005713; Fri, 16 Dec 2011 08:46:45 -0800 (PST) Received: by 10.216.21.196 with HTTP; Fri, 16 Dec 2011 08:46:45 -0800 (PST) In-Reply-To: References: <4EE90067.9020109@bopp.net> <0105D5C1E0353146B1B222348B0411A20A43E78632@NIHMLBX02.nih.gov> <4EEABDB8.4020307@cygwin.com> Date: Fri, 16 Dec 2011 16:47:00 -0000 Message-ID: Subject: Re: Symlinks and sharing a home directory between Windows and Linux From: Jon Clugston To: cygwin@cygwin.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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/msg00363.txt.bz2 On Fri, Dec 16, 2011 at 11:20 AM, Andrew DeFaria wrote: > On 12/15/2011 07:40 PM, Larry Hall (Cygwin) wrote: >> >> I'm having difficulty seeing how what you have described could work unle= ss >> the consumers of these files are looking for symlinks only, which your >> example above contradicts. =A0And both of the ".bashrc" files are regist= ering >> as plain files, so I think you're right that the file system on which th= ey >> reside is coming into play, assuming the output above is from Cygwin's '= ls'. >> =A0But even if you had ".bashrc" and ".bashrc.lnk" with the former being= a >> UNIX-form of symlink and the latter being the Cygwin one, I'd still expe= ct >> Cygwin to recognize ".bashrc" first and only go looking for the .lnk ver= sion >> if it couldn't find that. > > I would think that Cygwin should see the .lnk version first. No? I guess > not. I thought it worked that way before. This would be a performance disaster - forcing a check for 'x.lnk' every time the software tried to access file 'x'. I doubt that it worked that way before. >> >> The output of strace may convince you of that as well. ;-) =A0It might >> actually work as you describe it though if >> you can get Cygwin to think that it can't open the former. =A0I could see >> that being the case if the UNIX symlink was created by a user ID Cygwin >> didn't recognize, for example. > > I've backed off to using hardlinks which work on both systems but it does= n't > work for directories. > -- > Andrew DeFaria > Accept that some days you're the pigeon, and some days you're the statue. > > > -- > Problem reports: =A0 =A0 =A0 http://cygwin.com/problems.html > FAQ: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 http://cygwin.com/faq/ > Documentation: =A0 =A0 =A0 =A0 http://cygwin.com/docs.html > Unsubscribe info: =A0 =A0 =A0http://cygwin.com/ml/#unsubscribe-simple > -- 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