Received: (from major@localhost)
	by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id QAA00577
	for pups-liszt; Thu, 27 Apr 2000 16:20:01 +1000 (EST)
Received: from europe.std.com (europe.std.com [199.172.62.20])
	by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id QAA00567
	for <pups@minnie.cs.adfa.oz.au>; Thu, 27 Apr 2000 16:19:51 +1000 (EST)
Received: from world.std.com (bdc@world-f.std.com [199.172.62.5])
	by europe.std.com (8.9.3/8.9.3) with ESMTP id CAA13645;
	Thu, 27 Apr 2000 02:19:45 -0400 (EDT)
Received: from localhost (bdc@localhost)
	by world.std.com (8.9.3/8.9.3) with ESMTP id CAA19153;
	Thu, 27 Apr 2000 02:19:44 -0400 (EDT)
Date: Wed, 26 Apr 2000 23:19:43 -0700
From: Brian Chase <bdc@world.std.com>
To: Warren Toomey <wkt@cs.adfa.edu.au>
cc: pups@minnie.cs.adfa.oz.au
Subject: Re: History of Unix mv.
In-Reply-To: <200004270223.MAA11845@henry.cs.adfa.edu.au>
Message-ID: <Pine.SGI.4.21.0004262316570.10764-100000@world.std.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups@minnie.cs.adfa.edu.au
Precedence: bulk

On Thu, 27 Apr 2000, Warren Toomey wrote:
> In article by Brian Chase:

> > When was the "mv" command first updated to do a copy/remove for regular
> > files being moved across filesystems? 
> > -brian.
> 
> V2 mv(1) manual says files can't be moved across filesystems. V3 mv(1)
> manual doesn't say either way. V4 mv(1) manual says the file will be
> copied and the original deleted. V5 mv(1) source code exec's cp(1) when
> the destination is on a different filesystem.

So wait.  I need some clarification here.  When you say V2, V3, V4, etc..
do you mean 2nd Ed, 3rd Ed, 4th Ed Unix?

-brian.