Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <423980FB.9070802@byu.net>
Date: Thu, 17 Mar 2005 06:07:07 -0700
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: POSIX-compliance of link(2)
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to POSIX, creating a hardlink to a symlink is supposed to be
impossible, because link(2) is supposed to resolve symlinks before
performing the actual link.  See
http://www.opengroup.org/austin/mailarchives/ag/msg08153.html.

$ touch a
$ ln -s a b
$ link b c      # Bug: c should be a hard link to a, not b
$ ls -l a b c
- -rw-r--r--  1 eblake None 0 Mar 15 19:04 a
lrwxrwxrwx  2 eblake None 1 Mar 15 19:04 b -> a
lrwxrwxrwx  2 eblake None 1 Mar 15 19:04 c -> a

- --
Life is short - so eat dessert first!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCOYD684KuGfSFAYARAvD7AKDCuNgYMbh+/ABSGkVgYsQL8TpyogCfds5H
OCJpNzpvCqSv5RbLTuyoVY8=
=aOAm
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/