Main index | Section 1 | 日本語 | Deutsch | Options |
The options are as follows:
| |
Back up any existing files before overwriting them by renaming
them to
file .old.
See
| |
| |
Use
suffix
as the backup suffix if
| |
| |
Copy the file. If the target file already exists and the files are the same, then do not change the modification time of the target. If the target's file flags and mode need not to be changed, the target's inode change time is also unchanged. | |
| |
Copy the file.
This is actually the default.
The
| |
| |
Specify the
DESTDIR
(top of the file hierarchy) that the items are installed in to.
If
| |
| |
Create directories. Missing parent directories are created as required. | |
| |
Specify the target's file flags; see chflags(1) for a list of possible flags and their meanings. | |
| |
Specify a group. A numeric GID is allowed. | |
| |
When copying, calculate the digest of the files with
hash
to store in the
| |
none | No hash. This is the default. |
md5 | The MD5 cryptographic message digest. |
rmd160 | |
The RMD-160 cryptographic message digest. | |
sha1 | The SHA-1 cryptographic message digest. |
sha256 | |
The 256-bits SHA-2 cryptographic message digest of the file. | |
sha512 | |
The 512-bits SHA-2 cryptographic message digest of the file. | |
| |
Instead of copying the file make a link to the source. The type of the link is determined by the linkflags argument. Valid linkflags are: a (absolute), r (relative), h (hard), s (symbolic), m (mixed). Absolute and relative have effect only for symbolic links. Mixed links are hard links for files on the same filesystem, symbolic otherwise. | |
| |
Write the metadata associated with each item installed to metalog in an mtree(8) "full path" specification line. The metadata includes: the file name and file type, and depending upon other options, the owner, group, file flags, modification time, and tags. | |
| |
Specify an alternate mode. The default mode is set to rwxr-xr-x (0755). The specified mode may be either an octal or symbolic value; see chmod(1) for a description of possible mode values. | |
| |
Use the user database text file master.passwd and group database text file group from dbdir, rather than using the results from the system's getpwnam(3) and getgrnam(3) (and related) library calls. | |
| |
Specify an owner. A numeric UID is allowed. | |
| |
Preserve the access and modification times.
Copy the file, as if the
| |
| |
Safe copy.
Normally,
install
unlinks an existing target before installing the new file.
With the
| |
| |
install exec's the command strip(1) to strip binaries so that install can be portable over a large number of systems and binary types. See below for how install can be instructed to use another program to strip binaries. | |
| |
Specify the
mtree(8)
tags to write out for the file when using
| |
| |
Indicate that install is running unprivileged, and that it should not
try to change the owner, the group, or the file flags of the destination.
The information that would have been updated can be stored in a log
file with
| |
| |
Cause install to be verbose, showing files as they are installed or backed up. | |
By default, install preserves all file flags, with the exception of the "nodump" flag.
The install utility attempts to prevent moving a file onto itself.
Installing /dev/null creates an empty file.
If the
DONTSTRIP
environment variable is present,
install
will ignore any specification of the
INS@XXXX | |
If either
| |
Temporary files may be left in the target directory if install exits abnormally.
File flags cannot be set by fchflags(2) over a NFS file system. Other file systems do not have a concept of flags. The install utility will only warn when flags could not be set on a file system that does not support them.
The
install
utility with
INSTALL (1) | January 18, 2013 |
Main index | Section 1 | 日本語 | Deutsch | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.