JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 11 Express Image Packaging System Guide     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information


1.  Introduction to the Image Packaging System

2.  IPS Graphical User Interfaces

Using Package Manager

Package Manager Command Line Options

Using Web Install

Exporting Files Using Web Install

Using Web Install to Add Publishers and Install Packages

Using Update Manager

Update Manager Command Line Options

3.  Working With Packages

4.  Creating and Managing Images

A.  IPS Command Reference


Using Update Manager

Update Manager updates all installed packages to the newest version allowed by the constraints imposed on the system by installed packages and publisher configuration. This function is the same as the following functions:

Start Update Manager in one of the following ways:

Status bar

When updates are available, you should see a notification in the status bar. Click where indicated in the notification. The Update Manager icon is a stack of three boxes.

Menu bar

Choose System>Administration>Update Manager.

Command line

$ /usr/lib/pm-launch pm-updatemanager

The Updates window displays, and the update process starts:

  1. The system refreshes all catalogs.

  2. The system evaluates all installed packages to determine which packages have updates available.

    • If no packages have updates available, the message “No Updates Available” is displayed and processing stops.

    • If package updates are available, the packages to be updated are listed for your review. This is your last chance to click the Cancel button to abort the update.

  3. Click the Proceed button to continue with the update. The system downloads and installs all package updates.

    The following packages are updated first if they have updates available. Then any other packages are updated.


    By default, each package is updated from the publisher from which it was originally installed. If the original publisher is non-sticky, then a newer version of the package that is compatible with this image could be installed from another publisher. Use the Package Manager Manage Publishers window or the pkg set-publisher command to set a publisher as sticky or non-sticky.

    A new BE might be created if certain packages are updated. See Images and Boot Environments.

    If an error occurs at any time during the update process, the Details panel is expanded and the details of the error are displayed. An error status indicator is shown next to the failed stage.

  4. If the system created a new BE for the update, you can edit the default BE name. When you are satisfied with the BE name, click the Restart Now button to restart your system immediately. Click the Restart Later button to restart your system at a later time. You must restart to boot into the new BE. The new BE will be your default boot choice. Your current BE will be available as an alternate boot choice.

Update Manager Command Line Options

The following options are supported for the pm-updatemanager(1) command.

Table 2-2 Update Manager Command Options

--image-dir or -R dir
Operate on the image rooted at dir. The default behavior is to operate on the current image.

The following command updates the image at /aux0/example_root:

$ /usr/lib/pm-launch pm-updatemanager -R /aux0/example_root
--help or -h
Display command usage information.