Date: Mon, 5 Feb 2001 12:55:12 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Ruslan Ermilov <ru@FreeBSD.org>, Stephen McKay <mckay@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/bin/cp cp.1 Message-ID: <p05010400b6a498779e0a@[128.113.24.47]> In-Reply-To: <20010205123941.D65569@sunbay.com> References: <200102040202.f1422dJ34045@freefall.freebsd.org> <20010205123941.D65569@sunbay.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05010400b6a498779e0a>