svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
pkgask(8)
pkgask(8) System Administration Commands pkgask(8)
NAME
pkgask - stores answers to a SVR4 package request script
SYNOPSIS
pkgask [-d device] [-R root_path] -r response pkginst...
DESCRIPTION
pkgask allows the administrator to store answers to an interactive SVR4
package (one with a request script, that is, a user-created file that
must be named request). Invoking this command generates a response file
that is then used as input at installation time. The use of this re‐
sponse file prevents any interaction from occurring during installation
since the file already contains all of the information the package
needs.
OPTIONS
The following options are supported
-d device Run the request script for a package on device. device
can be a directory pathname or the identifiers for tape
or removable medium (for example, /var/tmp and
/dev/dsk/c1d0s0). The default device is the installa‐
tion spool directory.
-R root_path Define the full path name of a directory to use as the
root_path. All files, including package system informa‐
tion files, are relocated to a directory tree starting
in the specified root_path.
Note -
The root file system of any non-global zones must not
be referenced with the -R option. Doing so might dam‐
age 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).
-r response Identify a file or directory which should be created to
contain the responses to interaction with the package.
The name must be a full pathname. The file, or direc‐
tory of files, can later be used as input to the
pkgadd(8) command.
OPERANDS
The following operands are supported:
pkginst Specify the package instance, or list of instances for which
request scripts will be created. The token all may be used
to refer to all packages available on the source medium.
EXIT STATUS
0 Successful completion.
>0 An error occurred.
USAGE
The pkgask command is used with 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 managed using the
pkg(1) command. There is no direct equivalent to pkgask in IPS, as IPS
does not support interactive prompts during package installation.
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
SEE ALSO
pkginfo(1), pkgmk(1), pkgparam(1), pkgproto(1), pkgtrans(1), admin(5),
attributes(7), installf(8), pkgadd(8), pkgchk(8), pkgrm(8), removef(8)
NOTES
The -r option can be used to indicate a directory name as well as a
filename. The directory name is used to create numerous response files,
each sharing the name of the package with which it should be associ‐
ated. This would be used, for example, when you will be adding multiple
interactive packages with one invocation of pkgadd(8). Each package
would need a response file. To create multiple response files with the
same name as the package instance, name the directory in which the
files should be created and supply multiple instance names with the
pkgask command. When installing the packages, you will be able to iden‐
tify this directory to the pkgadd(8) command.
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 the -R option was added in Solaris 2.1.
The pkgask utility, including support for the -d and -r options, was
added to Solaris in Solaris 2.0.
Oracle Solaris 11.4 3 Jan 2025 pkgask(8)