This is the mail archive of the
mailing list for the Cygwin project.
RE: How to make `mv the hard way' fail
- From: Larry Hall <lh-no-personal-replies-please at cygwin dot com>
- To: "Ben Wing" <ben at 666 dot com>, "'Raye Raskin'" <rayer at pobox dot com>, <cygwin at cygwin dot com>
- Date: Mon, 13 Dec 2004 00:47:12 -0500
- Subject: RE: How to make `mv the hard way' fail
- References: <002901c4e0cc$63809d60$5709a443@c40624a> <019e01c4e0d5$6543e220$210110ac@NEEEEEEE>
- Reply-to: Cygwin List <cygwin at cygwin dot com>
At 12:34 AM 12/13/2004, you wrote:
>> If you have enough disk space you could do "cp -pr FROM TO"
>> followed by "rm -rf FROM" if there are no errors reported by
>> the cp command.
>> You could do a "diff -qr FROM TO" before the rm to feel even safer.
>> You could even write a little shell script that does the
>> above, name it mv, and put it in /usr/local/bin or some other
>> place that comes before mv.exe in your path.
>> If you really wanted to, that is.
>Maybe someone could add an option to `mv' to make it fail rather than
>copy/rm? E.g. --no-copy.
I expect this is a <http://cygwin.com/acronyms/#PTC> situation, especially
given that the current behavior was added using the same process.
So, feel free to offer a patch if you're so inclined.
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
838 Washington Street (508) 893-9889 - FAX
Holliston, MA 01746
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html