bin/133907: cp(1) wrongly reports errors in vacuous copy

[james at jrv.org]

>Number:         133907
>Category:       bin
>Synopsis:       cp(1) wrongly reports errors in vacuous copy
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Apr 22 08:00:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     James R. Van Artsdalen
>Release:        FreeBSD 8.0-CURRENT amd64
>Organization:
>Environment:
System: FreeBSD bigtex.housenet.jrv 8.0-CURRENT FreeBSD 8.0-CURRENT #0 r189099: Fri Feb 27 07:09:47 CST 2009 james at bigtex.housenet.jrv:/usr/obj/usr/src/sys/GENERIC amd64


	

8.0-current svn r189099 amd64

	<precise description of the problem (multiple lines)>
>Description:
>How-To-Repeat:

$ mkdir x y
$ cp -Rp x/ y
cp: utimes: y/x: No such file or directory
cp: chown: y/x: No such file or directory
cp: chmod: y/x: No such file or directory
cp: chflags: y/x: No such file or directory
$ 

Appears to affect only the vacuous case of arg x being an empty directory, and only if -p is used.

This error is seen in diskless boots in /etc/rc.initdiskless during boot.

>Fix:

	

>Release-Note:
>Audit-Trail:
>Unformatted: