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 .\" 4. 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
28 .\" From: @(#)install.1 8.1 (Berkeley) 6/6/93
65 .Ar file1 ... fileN directory
79 The file(s) are copied
82 option is specified) to the target file or directory.
83 If the destination is a directory, then the
87 with its original filename.
88 If the target file already exists, it is
96 An alternate backup suffix may be specified via the
100 The options are as follows:
101 .Bl -tag -width indent
103 Back up any existing files before overwriting them by renaming
105 .Ar file Ns Pa .old .
108 for specifying a different backup suffix.
112 as the backup suffix if
117 If the target file already exists and the files are the same,
118 then do not change the modification time of the target.
119 If the target's file flags and mode need not to be changed,
120 the target's inode change time is also unchanged.
123 This is actually the default.
126 option is only included for backwards compatibility.
130 (top of the file hierarchy) that the items are installed in to.
133 is in use, a leading string of
135 will be removed from the file names logged to the
137 This option does not affect where the actual files are installed.
140 Missing parent directories are created as required.
142 Specify the target's file flags; see
144 for a list of possible flags and their meanings.
147 A numeric GID is allowed.
149 When copying, calculate the digest of the files with
155 is given no hash is emitted.
157 .Bl -tag -width rmd160 -offset indent
162 The MD5 cryptographic message digest.
164 The RMD-160 cryptographic message digest.
166 The SHA-1 cryptographic message digest.
170 cryptographic message digest of the file.
174 cryptographic message digest of the file.
176 .It Fl l Ar linkflags
177 Instead of copying the file make a link to the source.
178 The type of the link is determined by the
194 Absolute and relative have effect only for symbolic links.
196 are hard links for files on the same filesystem, symbolic otherwise.
198 Write the metadata associated with each item installed to
204 The metadata includes: the file name and file type, and depending upon
205 other options, the owner, group, file flags, modification time, and tags.
207 Specify an alternate mode.
208 The default mode is set to rwxr-xr-x (0755).
209 The specified mode may be either an octal or symbolic value; see
211 for a description of possible mode values.
213 Use the user database text file
215 and group database text file
219 rather than using the results from the system's
223 (and related) library calls.
226 A numeric UID is allowed.
228 Preserve the access and modification times.
229 Copy the file, as if the
231 (compare and copy) option is specified,
232 except if the target file does not already exist or is different,
233 then preserve the access and modification times of the source file.
238 unlinks an existing target before installing the new file.
241 flag a temporary file is used and then renamed to be
243 The reason this is safer is that if the copy or
244 rename fails, the existing target is left untouched.
249 to strip binaries so that
251 can be portable over a large
252 number of systems and binary types.
255 can be instructed to use another program to strip binaries.
259 tags to write out for the file when using
262 Indicate that install is running unprivileged, and that it should not
263 try to change the owner, the group, or the file flags of the destination.
264 The information that would have been updated can be stored in a log
271 showing files as they are installed or backed up.
276 preserves all file flags, with the exception of the
282 utility attempts to prevent moving a file onto itself.
286 creates an empty file.
290 utility checks for the presence of the
292 environment variable and if present,
293 uses the assigned value as the program to run if and when the
295 option has been specified.
299 environment variable is present,
301 will ignore any specification of the
304 This is mainly for use in debugging the
308 .Bl -tag -width ".Pa INS@XXXX" -compact
312 option is specified, or the
316 option is used in conjunction with the
318 option, temporary files named
324 are created in the target directory.
331 moved files by default.
332 The default was changed to copy in
353 option has changed as of
355 and it now takes an argument.
356 Command lines that used the old
358 will get an error or in rare cases will append logs to the first of
359 multiple source files rather than installing it.
361 Temporary files may be left in the target directory if
365 File flags cannot be set by
367 over a NFS file system.
368 Other file systems do not have a concept of flags.
371 utility will only warn when flags could not be set on a file system
372 that does not support them.
378 falsely says a file is copied when