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
69 The file(s) are moved (or copied if the
71 option is specified) to the target file or directory.
72 If the destination is a directory, then the
76 with its original filename.
77 If the target file already exists, it is
85 An alternate backup suffix may be specified via the
89 The options are as follows:
90 .Bl -tag -width indent
92 Back up any existing files before overwriting them by renaming
97 for specifying a different backup suffix.
101 as the backup suffix if
106 If the target file already exists and the files are the same,
107 then don't change the modification time of the target.
110 This is actually the default.
113 option is only included for backwards compatibility.
116 Missing parent directories are created as required.
118 Specify the target's file flags; see
120 for a list of possible flags and their meanings.
123 A numeric GID is allowed.
128 Specify an alternate mode.
129 The default mode is set to rwxr-xr-x (0755).
130 The specified mode may be either an octal or symbolic value; see
132 for a description of possible mode values.
135 A numeric UID is allowed.
137 Preserve the modification time.
138 Copy the file, as if the
140 (compare and copy) option is specified,
141 except if the target file doesn't already exist or is different,
142 then preserve the modification time of the file.
147 unlinks an existing target before installing the new file.
150 flag a temporary file is used and then renamed to be
152 The reason this is safer is that if the copy or
153 rename fails, the existing target is left untouched.
158 to strip binaries so that
160 can be portable over a large
161 number of systems and binary types.
167 actually installs something.
172 preserves all file flags, with the exception of the
178 utility attempts to prevent moving a file onto itself.
182 creates an empty file.
186 utility exits 0 on success, and 1 otherwise.
188 .Bl -tag -width INS@XXXX -compact
192 option is specified, or the
196 option is used in conjuction with the
198 option, temporary files named
204 are created in the target directory.
221 Temporary files may be left in the target directory if
225 File flags cannot be set by
227 over a NFS file system. Other file systems do not have a concept of flags.
229 will only warn when flags could not be set on a file system
230 that does not support them.
235 falsely says a file is copied when