svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
pkgadd(8)
pkgadd(8) System Administration Commands pkgadd(8)
NAME
pkgadd - install SVR4 software packages onto the system
SYNOPSIS
pkgadd [-nv] [-a admin] [-G] [ [-M] -R root_path]
[-r response] [-V fs_file]
[-d device | -d datastream pkginst | all]
[pkginst | -Y category [, category]...]
pkgadd -s [-d device | -d datastream pkginst | all]
[pkginst | -Y category [, category]...]
DESCRIPTION
pkgadd installs the contents of a SVR4 software package from the dis‐
tribution medium or directory onto the system. Used without the -d de‐
vice source specifier, pkgadd looks in the default spool directory
(/var/spool/pkg) for the package. Used with the -s option, it writes
the package to a spool directory instead of installing it.
The pkgadd utility requires an amount of temporary space the size of
the package that is being installed. pkgadd determines which temporary
directory to use by checking for the existence of the $TMPDIR environ‐
ment variable. If $TMPDIR is not defined, pkgadd uses P_tmpdir from
stdio.h. P_tmpdir has a default of /var/tmp/.
Certain unbundled and third-party packages are no longer entirely com‐
patible with the latest version of pkgadd. These packages require user
interaction throughout the installation and not just at the very begin‐
ning, or require that their request scripts be run as the root user.
To install these older packages (released prior to Solaris 2.4), set
the following environment variable: NONABI_SCRIPTS=TRUE
As long as this environment variable is set, pkgadd permits keyboard
interaction throughout the installation and package request scripts are
run as root.
If you have package request scripts that require running as user root
(instead of noaccess [the default] or user install), use the
rscript_alt parameter in the admin(5) file to make an appropriate se‐
lection. See admin(5).
Note that, in Solaris 8 and Solaris 9, the default user when running a
request script was either root or nobody, depending on the operating
system's patch level. In the current release, the default user is noac‐
cess.
In their current implementations, pkgadd, pkgtrans(1) and other package
commands can process a datastream of up to 4 GB.
The -d, -Y, and pkginst arguments shown in the SYNOPSIS are described
under OPERANDS, following OPTIONS.
OPTIONS
The supported options are described as follows. The -d device source
specifier is described under OPERANDS, below.
-a admin
Define an installation administration file, admin, to be used in
place of the default administration file. The token none overrides
the use of any admin file, and thus forces interaction with the
user. Unless a full path name is given, pkgadd first looks in the
current working directory for the administration file. If the spec‐
ified administration file is not in the current working directory,
pkgadd looks in the /var/sadm/install/admin directory for the ad‐
ministration file.
-G
This option is deprecated.
-M
Instruct pkgadd not to use the $root_path/etc/vfstab file for de‐
termining the client's mount points. This option assumes the mount
points are correct on the server and it behaves consistently with
Solaris 2.5 and earlier releases.
-n
Installation occurs in non-interactive mode. Suppress output of the
list of installed files. The default mode is interactive.
-r response
Identify a file or directory which contains output from a previous
pkgask(8) session. This file supplies the interaction responses
that would be requested by the package in interactive mode. re‐
sponse must be a full pathname.
-R root_path
Define the full path name of a directory to use as the root_path.
All files, including package system information files, are relo‐
cated to a directory tree starting in the specified root_path. The
root_path may be specified when installing to a client from a
server (for example, /export/root/client1).
Note -
The root file system of any non-global zones must not be refer‐
enced with the -R option. Doing so might damage the global zone's
file system, might compromise the security of the global zone,
and might damage the non-global zone's file system. See zones(7).
-s spool
Write the package into the directory spool instead of installing
it.
-v
Trace all of the scripts that get executed by pkgadd, located in
the pkginst/install directory. This option is used for debugging
the procedural and non-procedural scripts.
-V fs_file
Specify an alternative fs_file to map the client's file systems.
For example, used in situations where the $root_path/etc/vfstab
file is non-existent or unreliable.
When executed without options or operands, pkgadd uses /var/spool/pkg
(the default spool directory).
OPERANDS
The following operands are supported:
Sources
By default, pkgadd looks in the /var/spool/pkg directory when searching
for instances of a package to install or spool. Optionally, the source
for the package instances to be installed or spooled can be specified
using:
-d device
-d datastream pkgname,... | all
Install or copy a package from device. device can be any of the
following:
o A full path name to a directory or the identifiers for
tape or removable medium (for example, /var/tmp).
o A datastream created by pkgtrans (see pkgtrans(1)).
The second form of the -d specifier, above, indicates the syntax
you use when specifying a datastream. In this case you must specify
either a comma-separated list of package names or the keyword all.
Instances
By default, pkgadd searches the specified source, and presents an in‐
teractive menu allowing the user to select which package instances
found on the source are to be installed. As an alternative, the package
instances to be installed can be specified using:
pkginst
The package instance or list of instances to be installed. The to‐
ken all may be used to refer to all packages available on the
source medium. The format pkginst.* can be used to indicate all in‐
stances of a package.
The asterisk character (*) is a special character to some shells
and may need to be escaped. In the C-Shell, the asterisk must be
surrounded by single quotes (') or preceded by a backslash (\).
-Y category[,category...]
Install packages based on the value of the CATEGORY parameter
stored in the package's pkginfo(5) file. All packages on the source
medium whose CATEGORY matches one of the specified categories will
be selected for installation or spooling.
EXAMPLES
Example 1 Installing a Package from a Solaris DVD
The following example installs a package from a Solaris DVD. You are
prompted for the name of the package you want to install.
example# pkgadd -d /cdrom/cdrom0/s0/Solaris_10/Product
Example 2 Installing a Set of Packages from a Datastream
The example command shown below installs all of the packages in the
datastream specified by the -d source specifier. Prior to this command,
this datastream must have been created with the pkgtrans(1) command.
example# pkgadd -d /var/tmp/datastream all
The keyword all specifies that all of the packages found in the desig‐
nated datastream will be installed.
EXIT STATUS
0
Successful completion
1
Fatal error.
2
Warning.
3
Interruption.
4
Administration.
5
Administration. Interaction is required. Do not use pkgadd -n.
10
Reboot after installation of all packages.
20
Reboot after installation of this package.
FILES
/var/sadm/install/logs/
Location where pkgadd logs an instance of software installation.
USAGE
The pkgadd command is used for installing legacy SVR4 packages created
for older Solaris releases. Packages designed for Solaris 11 and later
releases use the IPS package system instead, and are installed and man‐
aged using the pkg(1) command.
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE TYPEAT‐
TRIBUTE VALUE _ Availabilitypackage/svr4 _ Interface StabilityCommitted
SEE ALSO
pkginfo(1), pkgmk(1), pkgparam(1), pkgproto(1), pkgtrans(1), admin(5),
pkginfo(5), attributes(7), zones(7), installf(8), pkgadm(8), pkgask(8),
pkgchk(8), pkgrm(8), removef(8)
NOTES
When transferring a package to a spool directory, the -r, -n, and -a
options cannot be used.
The -r option can be used to indicate a directory name as well as a
filename. The directory can contain numerous response files, each shar‐
ing the name of the package with which it should be associated. This
would be used, for example, when adding multiple interactive packages
with one invocation of pkgadd. In this situation, each package would
need a response file. If you create response files with the same name
as the package (for example, pkinst1 and pkinst2), then name the direc‐
tory in which these files reside after the -r.
The -n option causes the installation to halt if any interaction is
needed to complete it.
If the default admin file is too restrictive, the administration file
may need to be modified to allow for total non-interaction during a
package installation. See admin(5) for details.
HISTORY
Support for package signatures, and for installation from http: or
https: URIs, including the -k, -P, and -x options, was added in Solaris
9 12/03 (Update 5) and removed in Oracle Solaris 11.4.60.
Support for the -G option was added in Solaris 10 3/05.
Support for the -Y option was added in Solaris 9.
Support for the -M, -V, and -v options was added in Solaris 2.6.
Support for the -R option was added in Solaris 2.1.
The pkgadd utility, including support for the -d, -a, -r, and -n op‐
tions, was added to Solaris in Solaris 2.0.
Oracle Solaris 11.4 3 Jan 2025 pkgadd(8)