Un outil pour savoir si une commande est posix - retour accueil
git clone git://bebou.netlib.re/isposix
Log | Files | Refs | README |
mv.html (23007B)
1 <!-- Copyright 2001-2024 IEEE and The Open Group, All Rights Reserved -->
2 <!DOCTYPE HTML>
3 <html lang="en">
4 <head>
5 <meta name="generator" content="HTML Tidy for HTML5 for Linux version 5.8.0">
6 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
7 <link type="text/css" rel="stylesheet" href="style.css"><!-- Generated by The Open Group rhtm tool v1.2.4 -->
8 <!-- Copyright (c) 2001-2024 The Open Group, All Rights Reserved -->
9 <title>mv</title>
10 </head>
11 <body bgcolor="white">
12 <div class="NAVHEADER">
13 <table summary="Header navigation table" class="nav" width="100%" border="0" cellpadding="0" cellspacing="0">
14 <tr class="nav">
15 <td class="nav" width="15%" align="left" valign="bottom"><a href="../utilities/msgfmt.html" accesskey="P"><<<
16 Previous</a></td>
17 <td class="nav" width="70%" align="center" valign="bottom"><a href="contents.html">Home</a></td>
18 <td class="nav" width="15%" align="right" valign="bottom"><a href="../utilities/newgrp.html" accesskey="N">Next
19 >>></a></td>
20 </tr>
21 </table>
22 <hr align="left" width="100%"></div>
23 <script language="JavaScript" src="../jscript/codes.js"></script><basefont size="3">
24 <center><font size="2">The Open Group Base Specifications Issue 8<br>
25 IEEE Std 1003.1-2024<br>
26 Copyright © 2001-2024 The IEEE and The Open Group</font></center>
27 <hr size="2" noshade>
28 <a name="top" id="top"></a> <a name="mv" id="mv"></a> <a name="tag_20_83" id="tag_20_83"></a><!-- mv -->
29 <h4 class="mansect"><a name="tag_20_83_01" id="tag_20_83_01"></a>NAME</h4>
30 <blockquote>mv — move files</blockquote>
31 <h4 class="mansect"><a name="tag_20_83_02" id="tag_20_83_02"></a>SYNOPSIS</h4>
32 <blockquote class="synopsis">
33 <p><code><tt>mv</tt> <b>[</b><tt>-if</tt><b>]</b> <i>source_file target_file</i> <tt><br>
34 <br>
35 mv</tt> <b>[</b><tt>-if</tt><b>]</b> <i>source_file</i><tt>...</tt> <i>target_dir</i> <tt><br></tt></code></p>
36 </blockquote>
37 <h4 class="mansect"><a name="tag_20_83_03" id="tag_20_83_03"></a>DESCRIPTION</h4>
38 <blockquote>
39 <p>In the first synopsis form, the <i>mv</i> utility shall move the file named by the <i>source_file</i> operand to the destination
40 specified by the <i>target_file</i>. This first synopsis form is assumed when the final operand does not name an existing directory
41 and is not a symbolic link referring to an existing directory. In this case, if <i>source_file</i> names a non-directory file and
42 <i>target_file</i> ends with a trailing <slash> character, <i>mv</i> shall treat this as an error and no <i>source_file</i>
43 operands shall be processed.</p>
44 <p>In the second synopsis form, <i>mv</i> shall move each file named by a <i>source_file</i> operand to a destination file in the
45 existing directory named by the <i>target_dir</i> operand, or referenced if <i>target_dir</i> is a symbolic link referring to an
46 existing directory. The destination path for each <i>source_file</i> shall be the concatenation of the target directory, a single
47 <slash> character if the target did not end in a <slash>, and the last pathname component of the <i>source_file</i>.
48 This second form is assumed when the final operand names an existing directory.</p>
49 <p>If any operand specifies an existing file of a type not specified by the System Interfaces volume of POSIX.1-2024, the behavior
50 is implementation-defined.</p>
51 <p>For each <i>source_file</i> the following steps shall be taken:</p>
52 <ol>
53 <li>
54 <p>If the destination path exists, the <b>-f</b> option is not specified, and either of the following conditions is true:</p>
55 <ol type="a">
56 <li>
57 <p>The permissions of the destination path do not permit writing and the standard input is a terminal.</p>
58 </li>
59 <li>
60 <p>The <b>-i</b> option is specified.</p>
61 </li>
62 </ol>
63 <p>the <i>mv</i> utility shall write a prompt to standard error and read a line from standard input. If the response is not
64 affirmative, <i>mv</i> shall do nothing more with the current <i>source_file</i> and go on to any remaining
65 <i>source_file</i>s.</p>
66 </li>
67 <li>
68 <p>If the <i>source_file</i> operand and destination path resolve to either the same existing directory entry or different
69 directory entries for the same existing file, then the destination path shall not be removed, and one of the following shall
70 occur:</p>
71 <ol type="a">
72 <li>
73 <p>No change is made to <i>source_file</i>, no error occurs, and no diagnostic is issued.</p>
74 </li>
75 <li>
76 <p>No change is made to <i>source_file</i>, a diagnostic is issued to standard error identifying the two names, and the exit status
77 is affected.</p>
78 </li>
79 <li>
80 <p>If the <i>source_file</i> operand and destination path name distinct directory entries, then the <i>source_file</i> operand is
81 removed, no error occurs, and no diagnostic is issued.</p>
82 </li>
83 </ol>
84 <p>The <i>mv</i> utility shall do nothing more with the current <i>source_file</i>, and go on to any remaining
85 <i>source_file</i>s.</p>
86 </li>
87 <li>
88 <p>The <i>mv</i> utility shall perform actions equivalent to the <a href="../functions/rename.html"><i>rename</i>()</a> function
89 defined in the System Interfaces volume of POSIX.1-2024, called with the following arguments:</p>
90 <ol type="a">
91 <li>
92 <p>The <i>source_file</i> operand is used as the <i>old</i> argument.</p>
93 </li>
94 <li>
95 <p>The destination path is used as the <i>new</i> argument.</p>
96 </li>
97 </ol>
98 <p>If this succeeds, <i>mv</i> shall do nothing more with the current <i>source_file</i> and go on to any remaining
99 <i>source_file</i>s. If this fails for any reasons other than those described for the <i>errno</i> [EXDEV] in the System Interfaces
100 volume of POSIX.1-2024, <i>mv</i> shall write a diagnostic message to standard error, do nothing more with the current
101 <i>source_file</i>, and go on to any remaining <i>source_file</i>s.</p>
102 </li>
103 <li>
104 <p>If the destination path exists, and it is a file of type directory and <i>source_file</i> is not a file of type directory, or it
105 is a file not of type directory and <i>source_file</i> is a file of type directory, <i>mv</i> shall write a diagnostic message to
106 standard error, do nothing more with the current <i>source_file</i>, and go on to any remaining <i>source_file</i>s. If the
107 destination path exists and was created by a previous step, it is unspecified whether this will treated as an error or the
108 destination path will be overwritten.</p>
109 </li>
110 <li>
111 <p>If the destination path exists, <i>mv</i> shall attempt to remove it. If this fails for any reason, <i>mv</i> shall write a
112 diagnostic message to standard error, do nothing more with the current <i>source_file</i>, and go on to any remaining
113 <i>source_file</i>s.</p>
114 </li>
115 <li>
116 <p>The file hierarchy rooted in <i>source_file</i> shall be duplicated as a file hierarchy rooted in the destination path. If
117 <i>source_file</i> or any of the files below it in the hierarchy are symbolic links, the links themselves shall be duplicated,
118 including their contents, rather than any files to which they refer. The following characteristics of each file in the file
119 hierarchy shall be duplicated:</p>
120 <ul>
121 <li>
122 <p>The time of last data modification and time of last access</p>
123 </li>
124 <li>
125 <p>The user ID and group ID</p>
126 </li>
127 <li>
128 <p>The file mode</p>
129 </li>
130 </ul>
131 <p>If the user ID, group ID, or file mode of a regular file cannot be duplicated, the file mode bits S_ISUID and S_ISGID shall not
132 be duplicated.</p>
133 <p>When files are duplicated to another file system, the implementation may require that the process invoking <i>mv</i> has read
134 access to each file being duplicated.</p>
135 <p>If files being duplicated to another file system have hard links to other files, it is unspecified whether the files copied to
136 the new file system have the hard links preserved or separate copies are created for the linked files.</p>
137 <p>If the duplication of the file hierarchy fails for any reason, <i>mv</i> shall write a diagnostic message to standard error, do
138 nothing more with the current <i>source_file</i>, and go on to any remaining <i>source_file</i>s.</p>
139 <p>If the duplication of the file characteristics fails for any reason, <i>mv</i> shall write a diagnostic message to standard
140 error, but this failure shall not cause <i>mv</i> to modify its exit status.</p>
141 </li>
142 <li>
143 <p>The file hierarchy rooted in <i>source_file</i> shall be removed. If this fails for any reason, <i>mv</i> shall write a
144 diagnostic message to the standard error, do nothing more with the current <i>source_file</i>, and go on to any remaining
145 <i>source_file</i>s.</p>
146 </li>
147 </ol>
148 </blockquote>
149 <h4 class="mansect"><a name="tag_20_83_04" id="tag_20_83_04"></a>OPTIONS</h4>
150 <blockquote>
151 <p>The <i>mv</i> utility shall conform to XBD <a href="../basedefs/V1_chap12.html#tag_12_02"><i>12.2 Utility Syntax
152 Guidelines</i></a> .</p>
153 <p>The following options shall be supported:</p>
154 <dl compact>
155 <dd></dd>
156 <dt><b>-f</b></dt>
157 <dd>Do not prompt for confirmation if the destination path exists. Any previous occurrence of the <b>-i</b> option is ignored.</dd>
158 <dt><b>-i</b></dt>
159 <dd>Prompt for confirmation if the destination path exists. Any previous occurrence of the <b>-f</b> option is ignored.</dd>
160 </dl>
161 <p>Specifying more than one of the <b>-f</b> or <b>-i</b> options shall not be considered an error. The last option specified shall
162 determine the behavior of <i>mv</i>.</p>
163 </blockquote>
164 <h4 class="mansect"><a name="tag_20_83_05" id="tag_20_83_05"></a>OPERANDS</h4>
165 <blockquote>
166 <p>The following operands shall be supported:</p>
167 <dl compact>
168 <dd></dd>
169 <dt><i>source_file</i></dt>
170 <dd>A pathname of a file or directory to be moved.</dd>
171 <dt><i>target_file</i></dt>
172 <dd>A new pathname for the file or directory being moved.</dd>
173 <dt><i>target_dir</i></dt>
174 <dd>A pathname of an existing directory into which to move the input files.</dd>
175 </dl>
176 </blockquote>
177 <h4 class="mansect"><a name="tag_20_83_06" id="tag_20_83_06"></a>STDIN</h4>
178 <blockquote>
179 <p>The standard input shall be used to read an input line in response to each prompt specified in the STDERR section. Otherwise,
180 the standard input shall not be used.</p>
181 </blockquote>
182 <h4 class="mansect"><a name="tag_20_83_07" id="tag_20_83_07"></a>INPUT FILES</h4>
183 <blockquote>
184 <p>The input files specified by each <i>source_file</i> operand can be of any file type.</p>
185 </blockquote>
186 <h4 class="mansect"><a name="tag_20_83_08" id="tag_20_83_08"></a>ENVIRONMENT VARIABLES</h4>
187 <blockquote>
188 <p>The following environment variables shall affect the execution of <i>mv</i>:</p>
189 <dl compact>
190 <dd></dd>
191 <dt><i>LANG</i></dt>
192 <dd>Provide a default value for the internationalization variables that are unset or null. (See XBD <a href=
193 "../basedefs/V1_chap08.html#tag_08_02"><i>8.2 Internationalization Variables</i></a> for the precedence of internationalization
194 variables used to determine the values of locale categories.)</dd>
195 <dt><i>LC_ALL</i></dt>
196 <dd>If set to a non-empty string value, override the values of all the other internationalization variables.</dd>
197 <dt><i>LC_COLLATE</i></dt>
198 <dd><br>
199 Determine the locale for the behavior of ranges, equivalence classes, and multi-character collating elements used in the extended
200 regular expression defined for the <b>yesexpr</b> locale keyword in the <i>LC_MESSAGES</i> category.</dd>
201 <dt><i>LC_CTYPE</i></dt>
202 <dd>Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as
203 opposed to multi-byte characters in arguments and input files), the behavior of character classes used in the extended regular
204 expression defined for the <b>yesexpr</b> locale keyword in the <i>LC_MESSAGES</i> category.</dd>
205 <dt><i>LC_MESSAGES</i></dt>
206 <dd><br>
207 Determine the locale used to process affirmative responses, and the locale used to affect the format and contents of diagnostic
208 messages and prompts written to standard error.</dd>
209 <dt><i>NLSPATH</i></dt>
210 <dd><sup>[<a href="javascript:open_code('XSI')">XSI</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border="0">
211 Determine the location of messages objects and message catalogs. <img src="../images/opt-end.gif" alt="[Option End]" border=
212 "0"></dd>
213 </dl>
214 </blockquote>
215 <h4 class="mansect"><a name="tag_20_83_09" id="tag_20_83_09"></a>ASYNCHRONOUS EVENTS</h4>
216 <blockquote>
217 <p>Default.</p>
218 </blockquote>
219 <h4 class="mansect"><a name="tag_20_83_10" id="tag_20_83_10"></a>STDOUT</h4>
220 <blockquote>
221 <p>Not used.</p>
222 </blockquote>
223 <h4 class="mansect"><a name="tag_20_83_11" id="tag_20_83_11"></a>STDERR</h4>
224 <blockquote>
225 <p>Prompts shall be written to the standard error under the conditions specified in the DESCRIPTION section. The prompts shall
226 contain the destination pathname, but their format is otherwise unspecified. Otherwise, the standard error shall be used only for
227 diagnostic messages.</p>
228 </blockquote>
229 <h4 class="mansect"><a name="tag_20_83_12" id="tag_20_83_12"></a>OUTPUT FILES</h4>
230 <blockquote>
231 <p>The output files may be of any file type.</p>
232 </blockquote>
233 <h4 class="mansect"><a name="tag_20_83_13" id="tag_20_83_13"></a>EXTENDED DESCRIPTION</h4>
234 <blockquote>
235 <p>None.</p>
236 </blockquote>
237 <h4 class="mansect"><a name="tag_20_83_14" id="tag_20_83_14"></a>EXIT STATUS</h4>
238 <blockquote>
239 <p>The following exit values shall be returned:</p>
240 <dl compact>
241 <dd></dd>
242 <dt> 0</dt>
243 <dd>All requested files (excluding files where a non-affirmative response was given to a request for confirmation) were
244 successfully moved.</dd>
245 <dt>>0</dt>
246 <dd>An error occurred.</dd>
247 </dl>
248 </blockquote>
249 <h4 class="mansect"><a name="tag_20_83_15" id="tag_20_83_15"></a>CONSEQUENCES OF ERRORS</h4>
250 <blockquote>
251 <p>If the copying or removal of <i>source_file</i> is prematurely terminated by a signal or error, <i>mv</i> may leave a partial
252 copy of <i>source_file</i> at the source or destination. The <i>mv</i> utility shall not modify both <i>source_file</i> and the
253 destination path simultaneously; termination at any point shall leave either <i>source_file</i> or the destination path
254 complete.</p>
255 </blockquote>
256 <hr>
257 <div class="box"><em>The following sections are informative.</em></div>
258 <h4 class="mansect"><a name="tag_20_83_16" id="tag_20_83_16"></a>APPLICATION USAGE</h4>
259 <blockquote>
260 <p>Some implementations mark for update the last file status change timestamp of renamed files and some do not. Applications which
261 make use of the last file status change timestamp may behave differently with respect to renamed files unless they are designed to
262 allow for either behavior.</p>
263 <p>The specification ensures that <i>mv</i> <b>a</b> <b>a</b> will not alter the contents of file <b>a</b>, and allows the
264 implementation to issue an error that a file cannot be moved onto itself. Likewise, when <b>a</b> and <b>b</b> are hard links to
265 the same file, <i>mv</i> <b>a</b> <b>b</b> will not alter <b>b</b>, but if a diagnostic is not issued, then it is unspecified
266 whether <b>a</b> is left untouched (as it would be by the <a href="../functions/rename.html"><i>rename</i>()</a> function) or
267 unlinked (reducing the link count of <b>b</b>).</p>
268 </blockquote>
269 <h4 class="mansect"><a name="tag_20_83_17" id="tag_20_83_17"></a>EXAMPLES</h4>
270 <blockquote>
271 <p>If the current directory contains only files <b>a</b> (of any type defined by the System Interfaces volume of POSIX.1-2024),
272 <b>b</b> (also of any type), and a directory <b>c</b>:</p>
273 <pre>
274 <tt>mv a b c
275 mv c d
276 </tt></pre>
277 <p>results with the original files <b>a</b> and <b>b</b> residing in the directory <b>d</b> in the current directory.</p>
278 </blockquote>
279 <h4 class="mansect"><a name="tag_20_83_18" id="tag_20_83_18"></a>RATIONALE</h4>
280 <blockquote>
281 <p>Early proposals diverged from the SVID and BSD historical practice in that they required that when the destination path exists,
282 the <b>-f</b> option is not specified, and input is not a terminal, <i>mv</i> fails. This was done for compatibility with <a href=
283 "../utilities/cp.html"><i>cp</i></a>. The current text returns to historical practice. It should be noted that this is consistent
284 with the <a href="../functions/rename.html"><i>rename</i>()</a> function defined in the System Interfaces volume of POSIX.1-2024,
285 which does not require write permission on the target.</p>
286 <p>For absolute clarity, paragraph (1), describing the behavior of <i>mv</i> when prompting for confirmation, should be interpreted
287 in the following manner:</p>
288 <pre>
289 <tt>if (exists AND (NOT f_option) AND
290 ((not_writable AND input_is_terminal) OR i_option))
291 </tt></pre>
292 <p>The <b>-i</b> option exists on BSD systems, giving applications and users a way to avoid accidentally unlinking files when
293 moving others. When the standard input is not a terminal, the 4.3 BSD <i>mv</i> deletes all existing destination paths without
294 prompting, even when <b>-i</b> is specified; this is inconsistent with the behavior of the 4.3 BSD <a href=
295 "../utilities/cp.html"><i>cp</i></a> utility, which always generates an error when the file is unwritable and the standard input is
296 not a terminal. The standard developers decided that use of <b>-i</b> is a request for interaction, so when the destination path
297 exists, the utility takes instructions from whatever responds to standard input.</p>
298 <p>The <a href="../functions/rename.html"><i>rename</i>()</a> function is able to move directories within the same file system.
299 Some historical versions of <i>mv</i> have been able to move directories, but not to a different file system. The standard
300 developers considered that this was an annoying inconsistency, so this volume of POSIX.1-2024 requires directories to be able to be
301 moved even across file systems. There is no <b>-R</b> option to confirm that moving a directory is actually intended, since such an
302 option was not required for moving directories in historical practice. Requiring the application to specify it sometimes, depending
303 on the destination, seemed just as inconsistent. The semantics of the <a href="../functions/rename.html"><i>rename</i>()</a>
304 function were preserved as much as possible. For example, <i>mv</i> is not permitted to "rename" files to or from directories,
305 even though they might be empty and removable.</p>
306 <p>Historic implementations of <i>mv</i> did not exit with a non-zero exit status if they were unable to duplicate any file
307 characteristics when moving a file across file systems, nor did they write a diagnostic message for the user. The former behavior
308 has been preserved to prevent scripts from breaking; a diagnostic message is now required, however, so that users are alerted that
309 the file characteristics have changed.</p>
310 <p>The exact format of the interactive prompts is unspecified. Only the general nature of the contents of prompts are specified
311 because implementations may desire more descriptive prompts than those used on historical implementations. Therefore, an
312 application not using the <b>-f</b> option or using the <b>-i</b> option relies on the system to provide the most suitable dialog
313 directly with the user, based on the behavior specified.</p>
314 <p>When <i>mv</i> is dealing with a single file system and <i>source_file</i> is a symbolic link, the link itself is moved as a
315 consequence of the dependence on the <a href="../functions/rename.html"><i>rename</i>()</a> functionality, per the DESCRIPTION.
316 Across file systems, this has to be made explicit.</p>
317 </blockquote>
318 <h4 class="mansect"><a name="tag_20_83_19" id="tag_20_83_19"></a>FUTURE DIRECTIONS</h4>
319 <blockquote>
320 <p>If this utility is directed to create a new directory entry that contains any bytes that have the encoded value of a
321 <newline> character, implementations are encouraged to treat this as an error. A future version of this standard may require
322 implementations to treat this as an error.</p>
323 </blockquote>
324 <h4 class="mansect"><a name="tag_20_83_20" id="tag_20_83_20"></a>SEE ALSO</h4>
325 <blockquote>
326 <p><a href="../utilities/cp.html#"><i>cp</i></a> , <a href="../utilities/ln.html#"><i>ln</i></a></p>
327 <p>XBD <a href="../basedefs/V1_chap08.html#tag_08"><i>8. Environment Variables</i></a> , <a href=
328 "../basedefs/V1_chap12.html#tag_12_02"><i>12.2 Utility Syntax Guidelines</i></a></p>
329 <p>XSH <a href="../functions/rename.html#"><i>rename</i></a></p>
330 </blockquote>
331 <h4 class="mansect"><a name="tag_20_83_21" id="tag_20_83_21"></a>CHANGE HISTORY</h4>
332 <blockquote>
333 <p>First released in Issue 2.</p>
334 </blockquote>
335 <h4 class="mansect"><a name="tag_20_83_22" id="tag_20_83_22"></a>Issue 6</h4>
336 <blockquote>
337 <p>The <i>mv</i> utility is changed to describe processing of symbolic links as specified in the IEEE P1003.2b draft
338 standard.</p>
339 <p>The APPLICATION USAGE section is added.</p>
340 </blockquote>
341 <h4 class="mansect"><a name="tag_20_83_23" id="tag_20_83_23"></a>Issue 7</h4>
342 <blockquote>
343 <p>Austin Group Interpretation 1003.1-2001 #016 is applied.</p>
344 <p>Austin Group Interpretation 1003.1-2001 #126 is applied, changing the description of the <i>LC_MESSAGES</i> environment
345 variable.</p>
346 <p>Austin Group Interpretations 1003.1-2001 #164, #168, and #169 are applied.</p>
347 <p>SD5-XCU-ERN-13 is applied, making an editorial correction to the SYNOPSIS.</p>
348 <p>SD5-XCU-ERN-51 is applied to the DESCRIPTION, defining the behavior for when files are being duplicated to another file system
349 while having hard links.</p>
350 <p>Changes are made related to support for finegrained timestamps.</p>
351 <p>POSIX.1-2008, Technical Corrigendum 1, XCU/TC1-2008/0124 [48] is applied.</p>
352 <p>POSIX.1-2008, Technical Corrigendum 2, XCU/TC2-2008/0147 [534] is applied.</p>
353 </blockquote>
354 <h4 class="mansect"><a name="tag_20_83_24" id="tag_20_83_24"></a>Issue 8</h4>
355 <blockquote>
356 <p>Austin Group Defect 251 is applied, encouraging implementations to disallow the creation of filenames containing any bytes that
357 have the encoded value of a <newline> character.</p>
358 <p>Austin Group Defect 1122 is applied, changing the description of <i>NLSPATH .</i></p>
359 <p>Austin Group Defect 1732 is applied, changing the EXIT STATUS section.</p>
360 </blockquote>
361 <div class="box"><em>End of informative text.</em></div>
362 <hr>
363 <p> </p>
364 <a href="#top"><span class="topOfPage">return to top of page</span></a><br>
365 <hr size="2" noshade>
366 <center><font size="2">UNIX® is a registered Trademark of The Open Group.<br>
367 POSIX™ is a Trademark of The IEEE.<br>
368 Copyright © 2001-2024 The IEEE and The Open Group, All Rights Reserved<br>
369 [ <a href="../mindex.html">Main Index</a> | <a href="../basedefs/contents.html">XBD</a> | <a href=
370 "../functions/contents.html">XSH</a> | <a href="../utilities/contents.html">XCU</a> | <a href="../xrat/contents.html">XRAT</a>
371 ]</font></center>
372 <hr size="2" noshade>
373 <div class="NAVHEADER">
374 <table summary="Header navigation table" class="nav" width="100%" border="0" cellpadding="0" cellspacing="0">
375 <tr class="nav">
376 <td class="nav" width="15%" align="left" valign="bottom"><a href="../utilities/msgfmt.html" accesskey="P"><<<
377 Previous</a></td>
378 <td class="nav" width="70%" align="center" valign="bottom"><a href="contents.html">Home</a></td>
379 <td class="nav" width="15%" align="right" valign="bottom"><a href="../utilities/newgrp.html" accesskey="N">Next
380 >>></a></td>
381 </tr>
382 </table>
383 <hr align="left" width="100%"></div>
384 </body>
385 </html>