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
| 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.\" $FreeBSD: head/bin/mv/mv.1 50471 1999-08-27 23:15:48Z peter $
| 36.\" $FreeBSD: head/bin/mv/mv.1 50544 1999-08-29 08:21:16Z mharo $
|
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
| 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.Op Fl v
|
47.Ar source target
48.Nm mv
49.Op Fl f | Fl i
| 48.Ar source target
49.Nm mv
50.Op Fl f | Fl i
|
| 51.Op Fl v
|
50.Ar source ... directory
51.Sh DESCRIPTION
52In its first form, the
53.Nm
54utility renames the file named by the
55.Ar source
56operand to the destination path named by the
57.Ar target
58operand.
59This form is assumed when the last operand does not name an already
60existing directory.
61.Pp
62In its second form,
63.Nm
64moves each file named by a
65.Ar source
66operand to a destination file in the existing directory named by the
67.Ar directory
68operand.
69The destination path for each operand is the pathname produced by the
70concatenation of the last operand, a slash, and the final pathname
71component of the named file.
72.Pp
73The following options are available:
74.Bl -tag -width flag
75.It Fl f
76Do not prompt for confirmation before overwriting the destination
77path.
78(The
79.Fl f
80option overrides any previous
81.Fl i
82options.)
83.It Fl i
84Cause
85.Nm
86to write a prompt to standard error before moving a file that would
87overwrite an existing file.
88If the response from the standard input begins with the character
89.Sq Li y
90or
91.Sq Li Y ,
92the move is attempted.
93(The
94.Fl i
95option overrides any previous
96.Fl f
97options.)
| 52.Ar source ... directory
53.Sh DESCRIPTION
54In its first form, the
55.Nm
56utility renames the file named by the
57.Ar source
58operand to the destination path named by the
59.Ar target
60operand.
61This form is assumed when the last operand does not name an already
62existing directory.
63.Pp
64In its second form,
65.Nm
66moves each file named by a
67.Ar source
68operand to a destination file in the existing directory named by the
69.Ar directory
70operand.
71The destination path for each operand is the pathname produced by the
72concatenation of the last operand, a slash, and the final pathname
73component of the named file.
74.Pp
75The following options are available:
76.Bl -tag -width flag
77.It Fl f
78Do not prompt for confirmation before overwriting the destination
79path.
80(The
81.Fl f
82option overrides any previous
83.Fl i
84options.)
85.It Fl i
86Cause
87.Nm
88to write a prompt to standard error before moving a file that would
89overwrite an existing file.
90If the response from the standard input begins with the character
91.Sq Li y
92or
93.Sq Li Y ,
94the move is attempted.
95(The
96.Fl i
97option overrides any previous
98.Fl f
99options.)
|
| 100.It Fl v
101Cause
102.Nm
103to be verbose, showing files after they are moved.
|
98.El
99.Pp
100It is an error for either the
101.Ar source
102operand or the destination path to specify a directory unless both do.
103.Pp
104If the destination path does not have a mode which permits writing,
105.Nm
106prompts the user for confirmation as specified for the
107.Fl i
108option.
109.Pp
110As the
111.Xr rename 2
112call does not work across file systems,
113.Nm
114uses
115.Xr cp 1
116and
117.Xr rm 1
118to accomplish the move.
119The effect is equivalent to:
120.Bd -literal -offset indent
121rm -f destination_path && \e
122\tcp -pRP source_file destination && \e
123\trm -rf source_file
124.Ed
125.Sh DIAGNOSTICS
126The
127.Nm
128utility exits 0 on success, and >0 if an error occurs.
129.Sh SEE ALSO
130.Xr cp 1 ,
131.Xr rm 1 ,
132.Xr symlink 7
133.Sh STANDARDS
134The
135.Nm
136utility is expected to be
137.St -p1003.2
138compatible.
139.Sh HISTORY
140A
141.Nm
142command appeared in
143.At v1 .
| 104.El
105.Pp
106It is an error for either the
107.Ar source
108operand or the destination path to specify a directory unless both do.
109.Pp
110If the destination path does not have a mode which permits writing,
111.Nm
112prompts the user for confirmation as specified for the
113.Fl i
114option.
115.Pp
116As the
117.Xr rename 2
118call does not work across file systems,
119.Nm
120uses
121.Xr cp 1
122and
123.Xr rm 1
124to accomplish the move.
125The effect is equivalent to:
126.Bd -literal -offset indent
127rm -f destination_path && \e
128\tcp -pRP source_file destination && \e
129\trm -rf source_file
130.Ed
131.Sh DIAGNOSTICS
132The
133.Nm
134utility exits 0 on success, and >0 if an error occurs.
135.Sh SEE ALSO
136.Xr cp 1 ,
137.Xr rm 1 ,
138.Xr symlink 7
139.Sh STANDARDS
140The
141.Nm
142utility is expected to be
143.St -p1003.2
144compatible.
145.Sh HISTORY
146A
147.Nm
148command appeared in
149.At v1 .
|