On Mon, 19 May 1997, Greg A. Woods wrote:

> Well, cp(1) may be the only utility affected by this change right now,
> but the result has been a serious amount of confusion and
> incompatibility with other POSIX compilant system in the behaviour of a
> number of other commands, such as the ls(1) example I posted earlier.

While these (and your other) points are certainly valid, they are really a
separate issue from the original poster's problem.  The old cp(1) had a
hidden bug, which is why it broke immediately upon the arrival of the
POSIX-compliancy change.

In other words, I'm not really disagreeing with you, just pointing out
that it has little bearing on the original problem here.

--scott