From: bdc@world.std.com (Brian Chase)
Subject: History of Unix mv.
Date: Wed, 26 Apr 2000 19:10:18 -0700 [thread overview]
Message-ID: <Pine.SGI.4.21.0004261906390.6381-100000@world.std.com> (raw)
When was the "mv" command first updated to do a copy/remove for regular
files being moved across filesystems?
-brian.
--- Brian Chase | bdc at world.std.com | http://world.std.com/~bdc/ -----
Received: (from major at localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id MAA98999
for pups-liszt; Thu, 27 Apr 2000 12:23:30 +1000 (EST)
Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au [131.236.21.158])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id MAA98993
for <pups at minnie.cs.adfa.oz.au>; Thu, 27 Apr 2000 12:23:18 +1000 (EST)
Received: (from wkt at localhost)
by henry.cs.adfa.edu.au (8.9.2/8.9.3) id MAA11845;
Thu, 27 Apr 2000 12:23:11 +1000 (EST)
(envelope-from wkt)
From: Warren Toomey <wkt@cs.adfa.edu.au>
Message-Id: <200004270223.MAA11845 at henry.cs.adfa.edu.au>
Subject: Re: History of Unix mv.
In-Reply-To: <Pine.SGI.4.21.0004261906390.6381-100000 at world.std.com> from Brian Chase at "Apr 26, 2000 7:10:18 pm"
To: bdc at world.std.com (Brian Chase)
Date: Thu, 27 Apr 2000 12:23:11 +1000 (EST)
Cc: pups at minnie.cs.adfa.oz.au
Reply-To: wkt at cs.adfa.edu.au
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups at minnie.cs.adfa.edu.au
Precedence: bulk
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.
Warren
Received: (from major at 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 at minnie.cs.adfa.oz.au>; Thu, 27 Apr 2000 16:19:51 +1000 (EST)
Received: from world.std.com (bdc at 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 at 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 at cs.adfa.edu.au>
cc: pups at minnie.cs.adfa.oz.au
Subject: Re: History of Unix mv.
In-Reply-To: <200004270223.MAA11845 at henry.cs.adfa.edu.au>
Message-ID: <Pine.SGI.4.21.0004262316570.10764-100000 at world.std.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-pups at 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.
Received: (from major at localhost)
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) id QAA00629
for pups-liszt; Thu, 27 Apr 2000 16:22:57 +1000 (EST)
Received: from henry.cs.adfa.edu.au (henry.cs.adfa.edu.au [131.236.21.158])
by minnie.cs.adfa.edu.au (8.9.3/8.9.3) with ESMTP id QAA00623
for <pups at minnie.cs.adfa.edu.au>; Thu, 27 Apr 2000 16:22:47 +1000 (EST)
Received: (from wkt at localhost)
by henry.cs.adfa.edu.au (8.9.2/8.9.3) id QAA13320;
Thu, 27 Apr 2000 16:22:42 +1000 (EST)
(envelope-from wkt)
From: Warren Toomey <wkt@cs.adfa.edu.au>
Message-Id: <200004270622.QAA13320 at henry.cs.adfa.edu.au>
Subject: Re: History of Unix mv.
In-Reply-To: <Pine.SGI.4.21.0004262316570.10764-100000 at world.std.com> from Brian Chase at "Apr 26, 2000 11:19:43 pm"
To: bdc at world.std.com (Brian Chase)
Date: Thu, 27 Apr 2000 16:22:42 +1000 (EST)
Cc: pups at minnie.cs.adfa.edu.au (Unix Heritage Society)
Reply-To: wkt at cs.adfa.edu.au
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-pups at minnie.cs.adfa.edu.au
Precedence: bulk
In article by Brian Chase:
> > 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.
Yup, 2nd Edition == 2e == V2.
1st Edition November 3, 1971
2nd Edition June 12, 1972
3rd Edition February, 1973
4th Edition November, 1973
5th Edition June, 1974
6th Edition May, 1975
7th Edition January, 1979
8th Edition February, 1985
9th Edition September, 1986
10th Edition October, 1989
Cheers,
Warren
reply other threads:[~2000-04-27 2:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SGI.4.21.0004261906390.6381-100000@world.std.com \
--to=bdc@world.std.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).