axf-os161 / man / bin / mv.html
mv.html
Raw
<!--
Copyright (c) 2000, 2001, 2002, 2003, 2004, 2005, 2008, 2009, 2013
	The President and Fellows of Harvard College.

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. 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 UNIVERSITY 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 UNIVERSITY 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.
-->
<html>
<head>
<title>mv</title>
<body bgcolor=#ffffff>
<h2 align=center>mv</h2>
<h4 align=center>OS/161 Reference Manual</h4>

<h3>Name</h3>
<p>
mv - rename or move files
</p>

<h3>Synopsis</h3>
<p>
<tt>/bin/mv</tt> <em>oldname</em> <em>newname</em>
</p>

<h3>Description</h3>
<p>
<tt>mv</tt> renames the filesystem object specified by
<em>oldname</em> so that it is subsequently named <em>newname</em>.
Both files and directories can be renamed or moved into other parts of
the filesystem tree. However, devices may not be renamed and
filesystem objects may not be moved across filesystems.
</p>

<p>
<tt>mv</tt> accepts no options.
</p>

<p>
Note that <tt>mv</tt> does <em>not</em> support the Unix idiom
<tt>mv file1 file2 ... destination-dir</tt> to move a number of files
at once. In particular, <tt>mv foo bar/</tt> will fail, probably with
"Is a directory".
</p>

<h3>Requirements</h3>
<p>
<tt>mv</tt> uses the following system calls:
<ul>
<li> <A HREF=../syscall/rename.html>rename</A>
<li> <A HREF=../syscall/write.html>write</A>
<li> <A HREF=../syscall/_exit.html>_exit</A>
</ul>
</p>

<p>
As the rename system call is generally not part of the basic system
calls assignment, <tt>mv</tt> will usually still not function after
the basic system calls assignment is complete.
This call is typically part of a later assignment, usually the file
system assignment.
Once you implement the system call you should be able to rename
objects within the same directory.
To move things between directories you will need to implement
cross-directory support for rename at the file system layer.
This may or may not be part of your file system assignment;
consult your course materials for specific information.
</p>

<h3>See Also</h3>
<p>
<A HREF=cp.html>cp</A>, <A HREF=ln.html>ln<A>
</p>

</body>
</html>