1 .\" Copyright (c) 1987, 1990, 1993
2 .\" The Regents of the University of California. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by the University of
15 .\" California, Berkeley and its contributors.
16 .\" 4. Neither the name of the University nor the names of its contributors
17 .\" may be used to endorse or promote products derived from this software
18 .\" without specific prior written permission.
20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .\" From: @(#)install.1 8.1 (Berkeley) 6/6/93
57 .Ar file1 ... fileN directory
66 The file(s) are copied
67 to the target file or directory.
68 If the destination is a directory, then the
72 with its original filename.
73 If the target file already exists, it is
81 An alternate backup suffix may be specified via the
85 The options are as follows:
86 .Bl -tag -width indent
88 Back up any existing files before overwriting them by renaming
93 for specifying a different backup suffix.
97 as the backup suffix if
102 If the target file already exists and the files are the same,
103 then don't change the modification time of the target.
106 This is actually the default.
109 option is only included for backwards compatibility.
112 Missing parent directories are created as required.
114 Specify the target's file flags; see
116 for a list of possible flags and their meanings.
119 A numeric GID is allowed.
124 Specify an alternate mode.
125 The default mode is set to rwxr-xr-x (0755).
126 The specified mode may be either an octal or symbolic value; see
128 for a description of possible mode values.
131 A numeric UID is allowed.
133 Preserve the modification time.
134 Copy the file, as if the
136 (compare and copy) option is specified,
137 except if the target file doesn't already exist or is different,
138 then preserve the modification time of the file.
143 unlinks an existing target before installing the new file.
146 flag a temporary file is used and then renamed to be
148 The reason this is safer is that if the copy or
149 rename fails, the existing target is left untouched.
154 to strip binaries so that
156 can be portable over a large
157 number of systems and binary types.
163 actually installs something.
168 preserves all file flags, with the exception of the
174 utility attempts to prevent moving a file onto itself.
178 creates an empty file.
182 utility exits 0 on success, and 1 otherwise.
184 .Bl -tag -width INS@XXXX -compact
188 option is specified, or the
192 option is used in conjuction with the
194 option, temporary files named
200 are created in the target directory.
205 moved files by default.
206 The default was changed to copy in
223 Temporary files may be left in the target directory if
227 File flags cannot be set by
229 over a NFS file system. Other file systems do not have a concept of flags.
231 will only warn when flags could not be set on a file system
232 that does not support them.
237 falsely says a file is copied when