Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Ben Wing" <ben AT 666 DOT com>
To:	"'Raye Raskin'" <rayer AT pobox DOT com>, <cygwin AT cygwin DOT com>
Subject:	RE: How to make `mv the hard way' fail
Date:	Sun, 12 Dec 2004 23:34:19 -0600
Message-ID:	<019e01c4e0d5$6543e220$210110ac@NEEEEEEE>
MIME-Version:	1.0
In-Reply-To:	<002901c4e0cc$63809d60$5709a443@c40624a>

> 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.



--
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/

- Raw text -