SGI symlink bug?

[John H Merritt]

In article <62307 at sgi.sgi.com> rpw3 at sgi.com (Rob Warnock) writes:
>But the ln(1) *program* does succeed, even with hard links.
Not if you don't have write permission to the directory.  Also, you
are warned when you have no write permission to the target file.

iris613 42> touch foo bar
iris613 43> chmod 0 foo bar
iris613 46> ls -li
18475 ----------   1 merritt  fire           0 Jun 15 09:44 bar
18469 ----------   1 merritt  fire           0 Jun 15 09:44 foo
iris613 47> ln foo bar
ln: bar: 0 mode? y
iris613 48> ls -li
18469 ----------   2 merritt  fire           0 Jun 15 09:44 bar
18469 ----------   2 merritt  fire           0 Jun 15 09:44 foo
iris613 49> rm foo bar
foo: 0 mode ? y
bar: 0 mode ? y

Remember we are modifying the directory entries.
Personally, I prefer that the files are clobbered and no warning issued.
The "Do what I say, not what I mean!" attitude.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
John H. Merritt                   #  Yesterday I knew nothing,
Applied Research Corporation      #  Today I know that.
merritt at iris613.gsfc.nasa.gov     #