Charles M. Hannum writes:

>If it ever worked, it was a bug.  The current behavior has been
>documented for at least 7 years.  (And I see no reason to believe it's

Is there a reason for this to be handled that way in NetBSD (apart
from, 4.4BSD does it so, probably)?
It is contradictory with the chmod(2) system call, which does change
the modes of a file a symlink points to and it seems to be different
from other Unix implementations (at least those I've tried), where
it does actually change the link target, as an innocent user would
expect, imho...

--mkb