pkgadd - transfer software package to the system

     pkgadd [ -n ] [ -a admin ] [ -d device ] [ -R root_path ]
          [ -r response ] [ pkginst1 [ pkginst2 ] ...]

     pkgadd -s spool [ -d device ] [ pkginst1 [ pkginst2 ] ... ]]


     pkgadd transfers the contents of a software package from the
     distribution medium or directory to install it onto the sys-
     tem.  Used without the  - d  option,  pkgadd  looks  in  the
     default  spool  directory  for the package (/var/spool/pkg).
     Used with the -s option, it reads the  package  to  a  spool
     directory instead of installing it.

     Certain unbundled and third-party  packages  are  no  longer
     entirely  compatible  with  the  latest  version of pkgadd .
     These packages require user interaction throughout the  ins-
     tallation and not just at the very beginning.

     To install these older packages (released prior  to  Solaris
     2.4), set the following environment variable:


     pkgadd will permit keyboard interaction throughout the  ins-
     tallation as long as this environment variable is set.

     -n         Installation occurs in non-interactive mode.  The
               default mode is interactive.

      - a admin   Define  an  installation  administration  file,
               admin, to be used in place of the default adminis-
               tration 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 direc-
               tory for the administration file.  If  the  speci-
               fied  administration  file  is  not in the current
               working   directory,   pkgadd   looks    in    the
               /var/sadm/install/admin directory for the adminis-
               tration file.

     -d device  Install or copy a package  from  device.   device
               can  be  a  full  path  name to a directory or the
               identifiers for tape,  floppy  disk  or  removable
               disk (for example, /var/tmp or /floppy/floppy_name
               ).  It can also be a device  alias  (for  example,

     -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

     -r response
               Identify a file or directory which contains output
               from  a  previous  pkgask session.  This file sup-
               plies the  interaction  responses  that  would  be
               requested  by  the  package  in  interactive mode.
               response must be a full pathname.

     - s spool   Reads  the  package  into  the  directory  spool
               instead of installing it.

     pkginst   Specify the package instance or list of  instances
               to  be  installed.   The  token all may be used to
               refer to all  packages  available  on  the  source
               medium.   The  format  pkginst.*   can  be used to
               indicate all instances of a package.

     When executed without options,  pkgadd  uses  /var/spool/pkg
     (the default spool directory).

     The following example installs a package from a Solaris  CD-
     ROM.   You are prompted for the name of the package you want
     to install.

          example% pkgadd -d /cdrom/Solaris_2_3/s0/Solaris_2.3

     pkginfo(1), pkgmk(1), pkgparam(1), pkgproto(1), pkgtrans(1),
     installf(1M), pkgask(1M), pkgrm(1M), removef(1M), admin(4)

     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 sharing 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.

     Each package would need a  response  file.   If  you  create
     response  files  with the same name as the package (that is,
     pkinst1 and pkinst2), then name the directory in which these
     files reside after the -r.

     The -n  option  causes  the  installation  to  halt  if  any
     interaction is needed to complete it.