Newsgroups: comp.os.msdos.programmer
Path: utzoo!utgpu!watserv1!watmath!mks.com!mks!eric
From: eric@mks.mks.com (Eric Gisin)
Subject: Re: "file cannot be copied onto itself"
Sender: eric@mks.com (Eric Gisin)
References: <2091@nyx.UUCP> <10478@pt.cs.cmu.edu>
In-Reply-To: ralf@b.gp.cs.cmu.edu's message of 15 Sep 90 02:47:26 GMT
Organization: Mortice Kern Systems Inc., Waterloo, Ontario, CANADA
Date: 17 Sep 90 19:00:00
Message-ID: <ERIC.90Sep17190000@mks.mks.com>

There is at least one network where DOS function 0x60 (get canonical path)
returns a garbage string and no error. I can't remember the network, but
we did encounter this problem in our "cp" program. The code to canonicalize
a pathname is not that complicated, about 60 lines of C.

And under PC-NFS, there is no way to determine if files are the
same if they are linked together on the UNIX file system.
