From owner-cvs-all Mon Feb 5 9:55:43 2001 Delivered-To: cvs-all@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 699EA37B491; Mon, 5 Feb 2001 09:55:16 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id MAA333298; Mon, 5 Feb 2001 12:55:14 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20010205123941.D65569@sunbay.com> References: <200102040202.f1422dJ34045@freefall.freebsd.org> <20010205123941.D65569@sunbay.com> Date: Mon, 5 Feb 2001 12:55:12 -0500 To: Ruslan Ermilov , Stephen McKay From: Garance A Drosihn Subject: Re: cvs commit: src/bin/cp cp.1 Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:39 PM +0200 2/5/01, Ruslan Ermilov wrote: >On Sat, Feb 03, 2001, Stephen McKay wrote: > > Log: >> In the hope of saving others from hours of tedious recovery work, >> document that cp still isn't very useful for recursive copies even >> with the -R flag. This is because hard links are broken by cp. >> >Shouldn't this be moved into the BUGS section of the manpage? I wouldn't think so, but then I have a hard time coming up with a reason that anyone WOULD expect 'cp' to recreate hard links. If you 'cp a b', it does not create a hard link between the two files. It just reads from 'a' and writes the data to 'b'. I'd expect a recursive copy of 'cp -r dira dirb' to do exactly the same thing, one file at a time. Why would it know about hard links? I do agree that it is a good idea to document this behavior, but I wouldn't call it a "bug". -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message