public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew DeFaria <Andrew@DeFaria.com>
To: cygwin@cygwin.com
Subject: Re: Symlinks and sharing a home directory between Windows and Linux
Date: Fri, 16 Dec 2011 16:21:00 -0000	[thread overview]
Message-ID: <jcfr4q$ulp$1@dough.gmane.org> (raw)
In-Reply-To: <4EEABDB8.4020307@cygwin.com>

On 12/15/2011 07:40 PM, Larry Hall (Cygwin) wrote:
> I'm having difficulty seeing how what you have described could work 
> unless the consumers of these files are looking for symlinks only, 
> which your example above contradicts.  And both of the ".bashrc" files 
> are registering as plain files, so I think you're right that the file 
> system on which they reside is coming into play, assuming the output 
> above is from Cygwin's 'ls'.  But 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 expect Cygwin to recognize 
> ".bashrc" first and only go looking for the .lnk version 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.
> The output of strace may convince you of that as well. ;-)  It might 
> actually work as you describe it though if
> you can get Cygwin to think that it can't open the former.  I 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 
doesn't work for directories.
-- 
Andrew DeFaria <http://defaria.com>
Accept that some days you're the pigeon, and some days you're the statue.


--
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

  reply	other threads:[~2011-12-16 16:21 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]
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 [this message]
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='jcfr4q$ulp$1@dough.gmane.org' \
    --to=andrew@defaria.com \
    --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).