Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Reply-To: Cygwin List Message-Id: <6.2.0.14.0.20041213004448.04e02d30@pop.prospeed.net> Date: Mon, 13 Dec 2004 00:47:12 -0500 To: "Ben Wing" , "'Raye Raskin'" , From: Larry Hall Subject: RE: How to make `mv the hard way' fail In-Reply-To: <019e01c4e0d5$6543e220$210110ac@NEEEEEEE> References: <002901c4e0cc$63809d60$5709a443 AT c40624a> <019e01c4e0d5$6543e220$210110ac AT NEEEEEEE> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" 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 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 Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/