If any virtual environments were configured through the use of Oracle Solaris Zones, the task got gradually more complicated with little automation available to the administrator.
More often than not, to ensure better consistency across the data center, administrators re-installed systems from scratch instead of spending hours trying to patch the systems.
In the process, it covers some of the basics that you should know to ensure an update goes successfully and safely.
Before we begin the process of updating a system, let's go through a quick overview of IPS.
Package constraints generally represent a dependency or a versioning issue.
For all package update operations, either a new BE is created or a backup BE is created before applying the software updates to the running BE.
Since we have chosen vpa4 as the future A.05.01 virtual partition, we need to find the boot path of vpa4 : When the virtual partitions are booted, they will continue and complete their update processes (the virtual partitions can be booed in any order).After the power to the system has been restored, press the Esc key to get to the Boot PROM prompt where After verifying the disk drive is detected by the Boot PROM, continue the initialization sequence by entering boot.When the boot process has completed, ensure that the drive was detected by the kernel by reviewing the kernel messages in /var/adm/syslog/In previous releases of the Oracle Solaris platform, administrators used SVR4 packaging to install software onto a system, and then they used a different set of commands to install patches to update the system.While the end result was an updated system, it was often a very time consuming and error-prone process because administrators had to do the heavy lifting themselves to research what packages should be installed, what patches and recommended patch clusters were needed, and in what order they needed to be applied.