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.10 1997/10/26 10:33:02 helbig 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 ... 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.) 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.Pp 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 . 144