[DragonFlyBSD - Bug #2443] (Closed) A bug in cp

[John Marino via Redmine <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>]

Issue #2443 has been updated by John Marino.

Status changed from New to Closed

fixed: http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/7cfd531a3bf703c2ef3f01a325d0f976c2294303
----------------------------------------
Bug #2443: A bug in cp
http://bugs.dragonflybsd.org/issues/2443

Author: Aleksej Lebedev
Status: Closed
Priority: Normal
Assignee: John Marino
Category: 
Target version: 


Hello!

I recently found a bug in cp in FreeBSD-7.3 that was corrected in FreeBSD-9.

I checked DragonflyBSD's cp and the bug's still there.

It's easy to reproduce:

$ uname -a
DragonFly jb.umc8.ru 3.0-RELEASE DragonFly v3.0.2.30.ge2c75-RELEASE #0: Sat Apr 21 21:10:43 CEST 2012     root@jb.umc8.ru:/usr/obj/usr/src/sys/X86_64_GENERIC  x86_64
$ rm -rf a b
$ mkdir a b
$ cp -rp a/ b/ 
cp: utimes: b/a: No such file or directory
cp: chown: b/a: No such file or directory
cp: chmod: b/a: No such file or directory
cp: chflags: b/a: No such file or directory


That's what how it works under FreeBSD-9:

$ uname -a
FreeBSD msk.umc8.ru 9.1-RC2 FreeBSD 9.1-RC2 #4: Sun Oct 28 21:29:09 MSK 2012     root@msk.umc8.ru:/usr/obj/usr/src/sys/GENERIC  amd64
$ rm -rf a b
$ mkdir a b
$ cp -rp a/ b/ 

This command actually doesn't do anything, but it causes a failure if the shell is executed with -e option.

--
Aleksej Lebedev


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account