Dan and Bart, I need to make any revisions to the existing <pkg image-update> documentation below for 2008.11 over the next week.
In particular, is there any support for non-global zones with the pkg image-update command for the 2008.11 release? If so, I need to describe that support in the text below. Also, will there be a one-off procedure for upgrading from 2008.05 to 2008.11, or will the standard <pkg image-update> command work for 2008.05 to 2008.11? Barbara Upgrading an Image or Boot Environment ------------------------------------------------------ Upgrading a Boot Environment The OpenSolaris 2008.11 release enables you to upgrade an installed boot environment by using the Image Packaging System. Use one of the following upgrade methods: ? You can use the PackageManager graphical user interface (GUI) to update all installed the packages in your image to the latest available version. See the screencast to learn how to use the PackageManager GUI. ? Alternately, you can use the pkg image-update command to perform this task. The syntax for the pkg image-update command is as follows: pkg image-update [-nv] The command upgrades all installed packages in the current boot environment to their latest available version. With the -n option, the command executes, but makes no persistent changes to the image. With the -v option, progress messages are displayed during the operation. Using either method, the upgrade process automatically creates a clone: a new, bootable environment. The upgrade process applies the upgrade changes to the clone instead of to the original boot environment. After successfully completing the changes to the clone and rebooting the system, the upgraded clone is provided as the default, active boot environment in the GRUB menu. The original boot environment remains on the GRUB menu as an alternate selection. Note A clone of the boot environment includes everything hierarchically under the main root dataset of the original boot environment. Shared file systems are not under the root dataset and are not cloned. Instead, the boot environment accesses the original shared file systems. After upgrading your system, you can use the beadm list command to see a list of the boot environments on the system, including the new boot environment that was created by the pkg image-update command. See the following example. os# pkg image-update A clone of opensolaris exists and has been updated and activated. On next boot the Boot Environment opensolaris-1 will be mounted on /. Reboot when ready to switch to this updated BE. os# beadm list BE Active Active on Mountpoint Space Name reboot Used ---- ------ --------- ---------- ----- opensolaris yes no legacy 57.5K opensolaris-1 no yes - 2.59G In this example, the initial boot environment created by the installer is named opensolaris. The boot environment created by the pkg image-update command is automatically named opensolaris-1. After rebooting to the upgraded boot environment, any inactive boot environment can be destroyed to save space by running the beadm destroy command. For instructions, see How to Destroy an Existing Boot Environment on page 14. For further information about the pkg command, see Image Packaging System Guide and the pkg(1) man page. _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
