Re: link(2) behaviour when creating a hardlink to a symlink

[ejc <eric.j.christeson@xxxxxxxxx>]

On Wed, Jun 11, 2008 at 3:27 PM, Jordan Gordeev <jgordeev@dir.bg> wrote:
> Cvs2svn, a package available in pkgsrc, doesn't extract successfully on
> DragonFly.
> During extraction, a link() syscall is made to create a hardlink to a
> symlink that points to a non-existent file. The link() call fails with
> ENOENT.
> I'd like to know if you think that behaviour to be a bug.

I looked up symbolic links in apue2 and link() is listed as a function
that follows symbolic links.  "If the function follows a symbolic
link, a pathname argument to the function refers to the file pionted
to by the symbolic link."
Looks like this behavior is correct.

eric