1.\" Copyright (c) 1989, 1990, 1993
2.\" The Regents of the University of California. 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.\"
35.\" @(#)mv.1 8.1 (Berkeley) 5/31/93
36.\" $Id: mv.1,v 1.3 1995/08/15 19:44:39 joerg Exp $
37.\"
38.Dd May 31, 1993
39.Dt MV 1
40.Os
41.Sh NAME
42.Nm mv
43.Nd move files
44.Sh SYNOPSIS
45.Nm mv
46.Op Fl f | Fl i
47.Ar source target
48.Nm mv
49.Op Fl f | Fl i
50.Ar source ... source directory
51.Sh DESCRIPTION
52.Pp
53In its first form, the
54.Nm mv
55utility renames the file named by the
56.Ar source
57operand to the destination path named by the
58.Ar target
59operand.
60This form is assumed when the last operand does not name an already
61existing directory.
62.Pp
63In its second form,
64.Nm mv
65moves each file named by a
66.Ar source
67operand to a destination file in the existing directory named by the
68.Ar directory
69operand.
70The destination path for each operand is the pathname produced by the
71concatenation of the last operand, a slash, and the final pathname
72component of the named file.
73.Pp
74The following options are available:
75.Bl -tag -width flag
76.It Fl f
77Do not prompt for confirmation before overwriting the destination
78path.
79(The
80.Fl i
81option is ignored if the
82.Fl f
83option is specified.)
84.It Fl i
85Causes
86.Nm mv
87to write a prompt to standard error before moving a file that would
88overwrite an existing file.
89If the response from the standard input begins with the character ``y'',
90the move is attempted.
91.El
92.Pp
93It is an error for either the
94.Ar source
95operand or the destination path to specify a directory unless both do.
96.Pp
97If the destination path does not have a mode which permits writing,
98.Nm mv
99prompts the user for confirmation as specified for the
100.Fl i
101option.
102.Pp
103As the
104.Xr rename 2
105call does not work across file systems,
106.Nm mv
107uses
108.Xr cp 1
109and
110.Xr rm 1
111to accomplish the move.
112The effect is equivalent to:
113.Bd -literal -offset indent
114rm -f destination_path && \e
115\tcp -pRP source_file destination && \e
116\trm -rf source_file
117.Ed
118.Pp
119The
120.Nm mv
121utility exits 0 on success, and >0 if an error occurs.
122.Sh SEE ALSO
123.Xr cp 1 ,
124.Xr symlink 7
125.Sh STANDARDS
126The
127.Nm mv
128utility is expected to be
129.St -p1003.2
130compatible.
2.\" The Regents of the University of California. 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.\"
35.\" @(#)mv.1 8.1 (Berkeley) 5/31/93
36.\" $Id: mv.1,v 1.3 1995/08/15 19:44:39 joerg Exp $
37.\"
38.Dd May 31, 1993
39.Dt MV 1
40.Os
41.Sh NAME
42.Nm mv
43.Nd move files
44.Sh SYNOPSIS
45.Nm mv
46.Op Fl f | Fl i
47.Ar source target
48.Nm mv
49.Op Fl f | Fl i
50.Ar source ... source directory
51.Sh DESCRIPTION
52.Pp
53In its first form, the
54.Nm mv
55utility renames the file named by the
56.Ar source
57operand to the destination path named by the
58.Ar target
59operand.
60This form is assumed when the last operand does not name an already
61existing directory.
62.Pp
63In its second form,
64.Nm mv
65moves each file named by a
66.Ar source
67operand to a destination file in the existing directory named by the
68.Ar directory
69operand.
70The destination path for each operand is the pathname produced by the
71concatenation of the last operand, a slash, and the final pathname
72component of the named file.
73.Pp
74The following options are available:
75.Bl -tag -width flag
76.It Fl f
77Do not prompt for confirmation before overwriting the destination
78path.
79(The
80.Fl i
81option is ignored if the
82.Fl f
83option is specified.)
84.It Fl i
85Causes
86.Nm mv
87to write a prompt to standard error before moving a file that would
88overwrite an existing file.
89If the response from the standard input begins with the character ``y'',
90the move is attempted.
91.El
92.Pp
93It is an error for either the
94.Ar source
95operand or the destination path to specify a directory unless both do.
96.Pp
97If the destination path does not have a mode which permits writing,
98.Nm mv
99prompts the user for confirmation as specified for the
100.Fl i
101option.
102.Pp
103As the
104.Xr rename 2
105call does not work across file systems,
106.Nm mv
107uses
108.Xr cp 1
109and
110.Xr rm 1
111to accomplish the move.
112The effect is equivalent to:
113.Bd -literal -offset indent
114rm -f destination_path && \e
115\tcp -pRP source_file destination && \e
116\trm -rf source_file
117.Ed
118.Pp
119The
120.Nm mv
121utility exits 0 on success, and >0 if an error occurs.
122.Sh SEE ALSO
123.Xr cp 1 ,
124.Xr symlink 7
125.Sh STANDARDS
126The
127.Nm mv
128utility is expected to be
129.St -p1003.2
130compatible.