Sun Microsystems, Inc.
spacerspacer
spacer www.sun.com docs.sun.com |
spacer
black dot
 
 
C.  Additional SvR4 Packaging Requirements (Reference) Solaris Live Upgrade Alternate Boot Environment Compliance  Previous   Contents   Next 
   
 

Upgrade Compliance With the Custom JumpStart Program

Custom JumpStart program compliance ensures that packages can be added and removed while being part of the traditional Solaris installation utilities, which are the following:

  • The custom JumpStart program

  • Solaris suninstall program

  • Solaris Web Start installation method

The custom JumpStart program compliance also ensures that the package can participate in Solaris upgrades. To be custom JumpStart program compliant, a package also must follow alternate root (/) requirements that are outlined in "Custom JumpStart Program and Solaris Live Upgrade Alternate Root (/) Requirements".

To be able to use the custom JumpStart program effectively, packages must be added or removed without the user being prompted for information. To prevent user interaction, set up a new administration file with the pkgadd command -a option. The -a option defines an installation administration file to be used in place of the default administration file. Using the default file might result in the user being prompted for more information. You can create an administration file that indicates to pkgadd that it should bypass these checks and install the package with user confirmation. The following examples show how to use the pkgadd administration file.

  • If no administration file is provided, pkgadd uses /var/sadm/install/admin/default. Using this file could result in user interaction.

    # pkgadd 
  • If a relative administration file is provided on the command line, pkgadd looks in /var/sadm/install/admin for the file name and uses it. In this example, the relative administration file is named nocheck and pkgadd looks for /var/sadm/install/admin/nocheck.

    # pkgadd -a nocheck 
  • If an absolute file is provided pkgadd uses it. In this example, pkgadd looks in /tmp/nocheck.

    # pkgadd -a /tmp/nocheck 

The following is an example of an installation administration file that prevents pkgadd from prompting the user for confirmation before installing the package.

mail=
instance=overwrite
partial=nocheck
runlevel=nocheck
idepend=nocheck
space=nocheck
setuid=nocheck
confiict=nocheck
action=nocheck
basedir=default

For details, see the man pages, admin(4) or pkgadd(1M).

 
 
 
  Previous   Contents   Next