pkgask - stores answers to a request script
pkgask [-d device] [-R root_path] -r response pkginst...
pkgask allows the administrator to store answers to an
interactive 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 response file prevents
any interaction from occurring during installation since the
file already contains all of the information the package
The following options are supported
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.
Define the full path name of a directory to use as the
root_path. All files, including package system infor-
mation files, are relocated to a directory tree start-
ing in the specified root_path.
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(1M) command.
The following operands are supported:
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
0 Successful completion.
>0 An error occurred.
See attributes(5) for descriptions of the following attri-
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
| Availability | SUNWcsu |
pkginfo(1), pkgmk(1), pkgparam(1), pkgproto(1), pkgtrans(1),
installf(1M), pkgadd(1M), pkgchk(1M), pkgrm(1M),
Application Packaging Developer's Guide
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 pack-
age 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(1M). 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 ins-
talling the packages, you will be able to identify this
directory to the pkgadd(1M) command.
If the default admin file is too restrictive, the adminis-
tration file may need to be modified to allow for total
non-interaction during a package installation. See admin(4)
Man(1) output converted with