[unix-history] / bin / mv / mv.1

.\" Copyright (c) 1989, 1990 The Regents of the University of California.
.\" All rights reserved.
.\"
.\" This code is derived from software contributed to Berkeley by
.\" the Institute of Electrical and Electronics Engineers, Inc.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\"    notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\"    notice, this list of conditions and the following disclaimer in the
.\"    documentation and/or other materials provided with the distribution.
.\" 3. All advertising materials mentioning features or use of this software
.\"    must display the following acknowledgement:
.\"	This product includes software developed by the University of
.\"	California, Berkeley and its contributors.
.\" 4. Neither the name of the University nor the names of its contributors
.\"    may be used to endorse or promote products derived from this software
.\"    without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
.\"	from: @(#)mv.1	6.9 (Berkeley) 7/27/91
.\"	$Id: mv.1,v 1.5 1993/09/22 00:34:25 jtc Exp $
.\"
.Dd July 27, 1991
.Dt MV 1
.Os
.Sh NAME
.Nm mv
.Nd move files
.Sh SYNOPSIS
.Nm mv
.Op Fl fi
.Ar source target
.Nm mv
.Op Fl fi
.Ar source ... target
.Sh DESCRIPTION
In its first form, the
.Nm mv
utility renames the file named by the
.Ar source
operand to the destination path named by the
.Ar target
operand.
This form is assumed when the last operand does not name an already
existing directory.
.Pp
In its second form,
.Nm mv
moves each file named by a
.Ar source
operand to a destination file in the existing directory named by the
.Ar directory
operand.
The destination path for each operand is the pathname produced by the
concatenation of the last operand, a slash, and the final pathname
component of the named file.
.Pp
The following options are available:
.Bl -tag -width flag
.It Fl f
Do not prompt for confirmation if the destination path exists.
Any previous occurances of the
.Fl i
option will be ignored.
.It Fl i
Prompt for confirmation if the destination path exists.
Any previous occurances of the 
.Fl f 
option will be ignored.
.El
.Pp
It is an error for either the
.Ar source
operand or the destination path to specify a directory unless both do.
.Pp
If the destination path does not have a mode which permits writing,
.Nm mv
prompts the user for confirmation.  If the response from the
standard input begins with the character 
.Sq y ,
the move is attempted.
.Pp
As the
.Xr rename  2
call does not work across file systems,
.Nm mv
uses
.Xr cp 1
and
.Xr rm 1
to accomplish the move.
The effect is equivalent to:
.Bd -literal -offset indent
rm -f destination_path && \e
\tcp -pr source_file destination && \e
\trm -rf source_file
.Ed
.Pp
The
.Nm mv
utility exits 0 on success, and >0 if an error occurs.
.Sh SEE ALSO
.Xr cp 1
.Sh STANDARDS
The
.Nm mv
utility conforms to 
.St -p1003.2-92 .
Commit	Line	Data
15637ed4 RG	1	.\" Copyright (c) 1989, 1990 The Regents of the University of California.
	2	.\" All rights reserved.
	3	.\"
	4	.\" This code is derived from software contributed to Berkeley by
	5	.\" the Institute of Electrical and Electronics Engineers, Inc.
	6	.\"
	7	.\" Redistribution and use in source and binary forms, with or without
	8	.\" modification, are permitted provided that the following conditions
	9	.\" are met:
	10	.\" 1. Redistributions of source code must retain the above copyright
	11	.\" notice, this list of conditions and the following disclaimer.
	12	.\" 2. Redistributions in binary form must reproduce the above copyright
	13	.\" notice, this list of conditions and the following disclaimer in the
	14	.\" documentation and/or other materials provided with the distribution.
	15	.\" 3. All advertising materials mentioning features or use of this software
	16	.\" must display the following acknowledgement:
	17	.\" This product includes software developed by the University of
	18	.\" California, Berkeley and its contributors.
	19	.\" 4. Neither the name of the University nor the names of its contributors
	20	.\" may be used to endorse or promote products derived from this software
	21	.\" without specific prior written permission.
	22	.\"
	23	.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
	24	.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
	25	.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
	26	.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
	27	.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
	28	.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
	29	.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
	30	.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
	31	.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
	32	.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
	33	.\" SUCH DAMAGE.
	34	.\"
e3f791dd C	35	.\" from: @(#)mv.1 6.9 (Berkeley) 7/27/91
e3f791dd C	36	.\" $Id: mv.1,v 1.5 1993/09/22 00:34:25 jtc Exp $
15637ed4 RG	37	.\"
	38	.Dd July 27, 1991
	39	.Dt MV 1
	40	.Os
	41	.Sh NAME
	42	.Nm mv
	43	.Nd move files
	44	.Sh SYNOPSIS
	45	.Nm mv
e3f791dd	46	.Op Fl fi
15637ed4 RG	47	.Ar source target
15637ed4 RG	48	.Nm mv
e3f791dd C	49	.Op Fl fi
e3f791dd C	50	.Ar source ... target
15637ed4	51	.Sh DESCRIPTION
15637ed4 RG	52	In its first form, the
	53	.Nm mv
	54	utility renames the file named by the
	55	.Ar source
	56	operand to the destination path named by the
	57	.Ar target
	58	operand.
	59	This form is assumed when the last operand does not name an already
	60	existing directory.
	61	.Pp
	62	In its second form,
	63	.Nm mv
	64	moves each file named by a
	65	.Ar source
	66	operand to a destination file in the existing directory named by the
	67	.Ar directory
	68	operand.
	69	The destination path for each operand is the pathname produced by the
	70	concatenation of the last operand, a slash, and the final pathname
	71	component of the named file.
	72	.Pp
	73	The following options are available:
	74	.Bl -tag -width flag
	75	.It Fl f
e3f791dd C	76	Do not prompt for confirmation if the destination path exists.
e3f791dd C	77	Any previous occurances of the
15637ed4	78	.Fl i
e3f791dd	79	option will be ignored.
15637ed4	80	.It Fl i
e3f791dd C	81	Prompt for confirmation if the destination path exists.
	82	Any previous occurances of the
	83	.Fl f
	84	option will be ignored.
15637ed4 RG	85	.El
	86	.Pp
	87	It is an error for either the
	88	.Ar source
	89	operand or the destination path to specify a directory unless both do.
	90	.Pp
	91	If the destination path does not have a mode which permits writing,
	92	.Nm mv
e3f791dd C	93	prompts the user for confirmation. If the response from the
	94	standard input begins with the character
	95	.Sq y ,
	96	the move is attempted.
15637ed4 RG	97	.Pp
	98	As the
	99	.Xr rename 2
	100	call does not work across file systems,
	101	.Nm mv
	102	uses
	103	.Xr cp 1
	104	and
	105	.Xr rm 1
	106	to accomplish the move.
	107	The effect is equivalent to:
	108	.Bd -literal -offset indent
	109	rm -f destination_path && \e
	110	\tcp -pr source_file destination && \e
	111	\trm -rf source_file
	112	.Ed
	113	.Pp
	114	The
	115	.Nm mv
	116	utility exits 0 on success, and >0 if an error occurs.
	117	.Sh SEE ALSO
	118	.Xr cp 1
	119	.Sh STANDARDS
	120	The
	121	.Nm mv
e3f791dd C	122	utility conforms to
e3f791dd C	123	.St -p1003.2-92 .