SGI symlink bug?
Kevin Kuehl
krk at cs.purdue.EDU
Fri Jun 15 05:28:25 AEST 1990
In article <62256 at sgi.sgi.com> vjs at rhyolite.wpd.sgi.com (Vernon Schryver) writes:
>I think the reason our `ln -s for bar` kills the target is because `ln foo
>bar` and `mv foo bar` are always effective in the SVR3 world. It seems to
>me that `ln` and `ln -s` should be as identical as possible, except in the
>nature of the link they make. It would be bad if `ln foo bar` would
>succeed where `ln -s foo bar` would fail.
I agree with Vernon. Although I think `ln -s for bar' should not
write over bar (I grew up in a BSD world), all of the SVR3 machines I
tried blew `bar' away. Since more of the world seems to be going SVR3
or SVR4 everyday, I would rather IRIX was consistent with them.
Just my opinion,
Kevin
krk at cs.purdue.edu
..!{decwrl,gatech,ucbvax}!purdue!krk
More information about the Comp.sys.sgi
mailing list