ln -s gives wrong error message on Ultrix 4.1
Johan Vromans
jv at mh.nl
Sat Apr 13 19:59:04 AEST 1991
In article <11998 at dog.ee.lbl.gov> envbvs at epb7.lbl.gov (Brian V. Smith) writes:
| In article <1991Apr11.080051.10756 at pronto.mh.nl>, jv at mh.nl (Johan Vromans)
| writes:
| |> [on a problem with "ln -s"] :
| |> I do not agree. To me, it is more logical to check source first. If
| |> you do not have a (valid) source, there is no need worrying about the
| |> destination.
| No, no, no. There is no reason that the source must exist when the symlink
| is created.
*IF* the semantics of symlinks do not require the source to be
present, then I agree fully. In this case, you may consider EPERM to
be an error, and ENOENT a warning. And errors take precedence over
warnings.
In the general situation of an input and output file, I thing checking
input before output is intuitive.
Johan
--
Johan Vromans jv at mh.nl via internet backbones
Multihouse Automatisering bv uucp: ..!{uunet,hp4nl}!mh.nl!jv
Doesburgweg 7, 2803 PL Gouda, The Netherlands phone/fax: +31 1820 62911/62500
------------------------ "Arms are made for hugging" -------------------------
More information about the Comp.unix.ultrix
mailing list