Add the DragonFly cvs id and perform general cleanups on cvs/rcs/sccs ids. Most
[dragonfly.git] / bin / mv / mv.1
CommitLineData
984263bc
MD
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: src/bin/mv/mv.1,v 1.15.2.5 2003/01/24 02:29:13 keramida Exp $
1de703da 37.\" $DragonFly: src/bin/mv/mv.1,v 1.2 2003/06/17 04:22:50 dillon Exp $
984263bc
MD
38.\"
39.Dd July 9, 2002
40.Dt MV 1
41.Os
42.Sh NAME
43.Nm mv
44.Nd move files
45.Sh SYNOPSIS
46.Nm
47.Op Fl f | i | n
48.Op Fl v
49.Ar source target
50.Nm
51.Op Fl f | i | n
52.Op Fl v
53.Ar source ... directory
54.Sh DESCRIPTION
55In its first form, the
56.Nm
57utility renames the file named by the
58.Ar source
59operand to the destination path named by the
60.Ar target
61operand.
62This form is assumed when the last operand does not name an already
63existing directory.
64.Pp
65In its second form,
66.Nm
67moves each file named by a
68.Ar source
69operand to a destination file in the existing directory named by the
70.Ar directory
71operand.
72The destination path for each operand is the pathname produced by the
73concatenation of the last operand, a slash, and the final pathname
74component of the named file.
75.Pp
76The following options are available:
77.Bl -tag -width indent
78.It Fl f
79Do not prompt for confirmation before overwriting the destination
80path.
81(The
82.Fl f
83option overrides any previous
84.Fl i
85or
86.Fl n
87options.)
88.It Fl i
89Cause
90.Nm
91to write a prompt to standard error before moving a file that would
92overwrite an existing file.
93If the response from the standard input begins with the character
94.Ql y
95or
96.Ql Y ,
97the move is attempted.
98(The
99.Fl i
100option overrides any previous
101.Fl f
102or
103.Fl n
104options.)
105.It Fl n
106Do not overwrite an existing file.
107(The
108.Fl n
109option overrides any previous
110.Fl f
111or
112.Fl i
113options.)
114.It Fl v
115Cause
116.Nm
117to be verbose, showing files after they are moved.
118.El
119.Pp
120It is an error for either the
121.Ar source
122operand or the destination path to specify a directory unless both do.
123.Pp
124If the destination path does not have a mode which permits writing,
125.Nm
126prompts the user for confirmation as specified for the
127.Fl i
128option.
129.Pp
130As the
131.Xr rename 2
132call does not work across file systems,
133.Nm
134uses
135.Xr cp 1
136and
137.Xr rm 1
138to accomplish the move.
139The effect is equivalent to:
140.Bd -literal -offset indent
141rm -f destination_path && \e
142cp -pRP source_file destination && \e
143rm -rf source_file
144.Ed
145.Sh DIAGNOSTICS
146.Ex -std
147.Sh SEE ALSO
148.Xr cp 1 ,
149.Xr rm 1 ,
150.Xr symlink 7
151.Sh COMPATIBILITY
152The
153.Fl n
154and
155.Fl v
156options are non-standard and their use in scripts is not recommended.
157.Sh STANDARDS
158The
159.Nm
160utility is expected to be
161.St -p1003.2
162compatible.
163.Sh HISTORY
164A
165.Nm
166command appeared in
167.At v1 .