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. Neither the name of the University nor the names of its contributors
13 .\" may be used to endorse or promote products derived from this software
14 .\" without specific prior written permission.
16 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
62 .Ar file1 ... fileN directory
76 The file(s) are copied
79 option is specified) to the target file or directory.
80 If the destination is a directory, then the
84 with its original filename.
85 If the target file already exists, it is
93 An alternate backup suffix may be specified via the
97 The options are as follows:
98 .Bl -tag -width indent
102 as the backup suffix if
106 Back up any existing files before overwriting them by renaming
108 .Ar file Ns Pa .old .
111 for specifying a different backup suffix.
114 If the target file already exists and the files are the same,
115 then do not change the modification time of the target.
116 If the target's file flags and mode need not to be changed,
117 the target's inode change time is also unchanged.
120 This is actually the default.
123 option is only included for backwards compatibility.
127 (top of the file hierarchy) that the items are installed in to.
130 is in use, a leading string of
132 will be removed from the file names logged to the
134 This option does not affect where the actual files are installed.
137 Missing parent directories are created as required.
139 Specify the target's file flags; see
141 for a list of possible flags and their meanings.
144 A numeric GID is allowed.
146 When copying, calculate the digest of the files with
152 is given no hash is emitted.
154 .Bl -tag -width rmd160 -offset indent
159 The MD5 cryptographic message digest.
161 The RMD-160 cryptographic message digest.
163 The SHA-1 cryptographic message digest.
165 The 256-bits SHA-2 cryptographic message digest of the file.
167 The 512-bits SHA-2 cryptographic message digest of the file.
169 .It Fl l Ar linkflags
170 Instead of copying the file make a link to the source.
171 The type of the link is determined by the
187 Absolute and relative have effect only for symbolic links.
189 are hard links for files on the same filesystem, symbolic otherwise.
191 Write the metadata associated with each item installed to
197 The metadata includes: the file name and file type, and depending upon
198 other options, the owner, group, file flags, modification time, and tags.
200 Specify an alternate mode.
201 The default mode is set to rwxr-xr-x (0755).
202 The specified mode may be either an octal or symbolic value; see
204 for a description of possible mode values.
206 Use the user database text file
208 and group database text file
212 rather than using the results from the system's
216 (and related) library calls.
219 A numeric UID is allowed.
221 Preserve the access and modification times.
222 Copy the file, as if the
224 (compare and copy) option is specified,
225 except if the target file does not already exist or is different,
226 then preserve the access and modification times of the source file.
228 Flush each file to disk after copying.
229 This has a non-negligible impact on performance, but reduces the risk
230 of being left with a partial file if the system crashes or loses power
237 also enabled the use of temporary files to ensure atomicity when
238 replacing an existing target.
239 Temporary files are no longer optional.
244 to strip binaries so that
246 can be portable over a large
247 number of systems and binary types.
250 can be instructed to use another program to strip binaries.
254 tags to write out for the file when using
257 Indicate that install is running unprivileged, and that it should not
258 try to change the owner, the group, or the file flags of the destination.
259 The information that would have been updated can be stored in a log
266 showing files as they are installed or backed up.
271 preserves all file flags, with the exception of the
277 utility attempts to prevent moving a file onto itself.
281 creates an empty file.
285 utility checks for the presence of the
287 environment variable and if present,
288 uses the assigned value as the program to run if and when the
290 option has been specified.
294 environment variable is present,
296 will ignore any specification of the
299 This is mainly for use in debugging the
303 .Bl -tag -width "INS@XXXXXX" -compact
305 Temporary files named
311 are created in the target directory.
318 moved files by default.
319 The default was changed to copy in
340 option has changed as of
342 and it now takes an argument.
343 Command lines that used the old
345 will get an error or in rare cases will append logs to the first of
346 multiple source files rather than installing it.
348 Temporary files may be left in the target directory if
352 File flags cannot be set by
354 over a NFS file system.
355 Other file systems do not have a concept of flags.
358 utility will only warn when flags could not be set on a file system
359 that does not support them.
365 falsely says a file is copied when