public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Paul Bibbings <paul.bibbings@gmail.com>
To: cygwin-talk@cygwin.com
Subject: Re: link (corutils) 8.4-2: doesn't link
Date: Mon, 12 Apr 2010 14:57:00 -0000	[thread overview]
Message-ID: <87eiikzpkr.fsf@gmail.com> (raw)
In-Reply-To: <20100412143922.GB28908@calimero.vinschen.de>

Corinna Vinschen <corinna...@cygwin.com> writes:

> On Apr 12 15:15, Paul Bibbings wrote:
>> In the past I have used corutils' link without any problem.  I can't
>> recall when I last did use it successfully, but certainly prior to
>> Cygwin 1.7.  At the moment, however, link is not actually linking, but
>> appears rather to be creating a simple copy of the file linked to, as
>> the following illustrates (on Windows Vista):
>> 
>>    14:57:11 Paul Bibbings@JIJOU
>>    /cygdrive/d/Downloads/link_test $cp /usr/bin/zoo.exe zoo.exe
>> 
>>    14:57:37 Paul Bibbings@JIJOU
>>    /cygdrive/d/Downloads/link_test $link zoo.exe zoo_link
>> 
>>    14:57:54 Paul Bibbings@JIJOU
>>    /cygdrive/d/Downloads/link_test $ls -l
>>    total 128
>>    -rwxr-xr-x+ 2 Paul Bibbings None 65024 Apr 12 14:57 zoo.exe
>>    -rwxr-xr-x+ 2 Paul Bibbings None 65024 Apr 12 14:57 zoo_link.exe
>
> Looks exactly as expected.  Notice the link count.  if you us `ls -li'
> you will also see that both directory entries have the same inode number,
> so they are referring to the same file.  What's your problem again?

Only my ignorance, it seems!  I promise I won't post again until I've
served my penance. How long is it, again, in the sin bin for
stoopidity? :-)

Regards

Paul Bibbings

       reply	other threads:[~2010-04-12 14:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87mxx8zric.fsf@gmail.com>
     [not found] ` <20100412143922.GB28908@calimero.vinschen.de>
2010-04-12 14:57   ` Paul Bibbings [this message]
2010-04-15 18:05     ` Warren Young

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=87eiikzpkr.fsf@gmail.com \
    --to=paul.bibbings@gmail.com \
    --cc=cygwin-talk@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).