pkgask(1M) manual page
Table of Contents
pkgask - stores answers to a request script
pkgask [ -d device
] [ -R root_path ] -r response pkginst1 [ pkginst2 ]...]
SUNWcsu
pkgask allows the administrator to store answers to an interactive
package (one with a request script). Invoking this command generates a response
file that is then used as input at installation time. The use of this response
file prevents any interaction from occurring during installation since
the file already contains all of the information the package needs.
- -d
device
- Run the request script for a package on device. device can be a directory
pathname or the identifiers for tape, floppy disk or removable disk (for
example, /var/tmp, /dev/diskette, and /dev/dsk/c1d0s0). The default device
is the installation spool directory.
- -R root_path
- Define the full path name
of a subdirectory to use as the root_path. All files, including package
system information files, are relocated to a directory tree starting in
the specified root_path.
- -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 directory of files, can later
be used as input to the pkgadd command.
- 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.
pkginfo(1)
, pkgmk(1)
, pkgparam(1)
, pkgproto(1)
, pkgtrans(1)
, installf(1M)
,
pkgadd(1M)
, pkgchk(1M)
, pkgrm(1M)
, removef(1M)
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 associated. This would be used, for example,
when you will be adding multiple interactive packages with one invocation
of pkgadd. 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 identify
this directory to the pkgadd command.
Table of Contents