Skip Navigation Links | |
Exit Print View | |
System Administration Guide: Oracle Solaris Containers-Resource Management and Oracle Solaris Zones Oracle Solaris Legacy Containers |
1. Introduction to Solaris 10 Resource Management
2. Projects and Tasks (Overview)
3. Administering Projects and Tasks
4. Extended Accounting (Overview)
5. Administering Extended Accounting (Tasks)
6. Resource Controls (Overview)
7. Administering Resource Controls (Tasks)
8. Fair Share Scheduler (Overview)
9. Administering the Fair Share Scheduler (Tasks)
10. Physical Memory Control Using the Resource Capping Daemon (Overview)
11. Administering the Resource Capping Daemon (Tasks)
13. Creating and Administering Resource Pools (Tasks)
14. Resource Management Configuration Example
15. Resource Control Functionality in the Solaris Management Console
16. Introduction to Solaris Zones
17. Non-Global Zone Configuration (Overview)
18. Planning and Configuring Non-Global Zones (Tasks)
19. About Installing, Halting, Cloning, and Uninstalling Non-Global Zones (Overview)
20. Installing, Booting, Halting, Uninstalling, and Cloning Non-Global Zones (Tasks)
21. Non-Global Zone Login (Overview)
22. Logging In to Non-Global Zones (Tasks)
23. Moving and Migrating Non-Global Zones (Tasks)
24. Oracle Solaris 10 9/10: Migrating a Physical Oracle Solaris System Into a Zone (Tasks)
25. About Packages and Patches on an Oracle Solaris System With Zones Installed (Overview)
What's New in Packaging and Patching When Zones Are Installed
Packaging and Patch Tools Overview
Patches Generated for Packages
Package Operations Possible in the Global Zone
Package Operations Possible in a Non-Global Zone
How Zone State Affects Patch and Package Operations
About Adding Packages in Zones
Using pkgadd in the Global Zone
Adding a Package to the Global Zone and to All Non-Global Zones
Adding a Package to the Global Zone Only
Adding a Package Installed in the Global Zone to all Non-Global Zones
Using pkgadd in a Non-Global Zone
About Removing Packages in Zones
Using pkgrm in the Global Zone
Removing a Package From the Global Zone and From all Non-Global Zones
Using pkgrm in a Non-Global Zone
Setting Package Parameters for Zones
SUNW_PKG_ALLZONES Package Parameter
SUNW_PKG_HOLLOW Package Parameter
SUNW_PKG_THISZONE Package Parameter
Oracle Solaris 10 8/07: Deferred Activation Patching
Oracle Solaris 10 10/09: Zones Parallel Patching to Reduce Patching Time
Applying Patches on an Oracle Solaris System With Zones Installed
Using patchadd in the Global Zone
Using patchadd in a Non-Global Zone
Interaction of patchadd -G and the pkginfo Variable on a System With Zones
Removing Patches on an Oracle Solaris System With Zones Installed
Using patchrm in the Global Zone
Using patchrm in a Non-Global Zone
27. Oracle Solaris Zones Administration (Overview)
28. Oracle Solaris Zones Administration (Tasks)
29. Upgrading an Oracle Solaris 10 System That Has Installed Non-Global Zones
30. Troubleshooting Miscellaneous Oracle Solaris Zones Problems
31. About Branded Zones and the Linux Branded Zone
32. Planning the lx Branded Zone Configuration (Overview)
33. Configuring the lx Branded Zone (Tasks)
34. About Installing, Booting, Halting, Cloning, and Uninstalling lx Branded Zones (Overview)
35. Installing, Booting, Halting, Uninstalling and Cloning lx Branded Zones (Tasks)
36. Logging In to lx Branded Zones (Tasks)
37. Moving and Migrating lx Branded Zones (Tasks)
38. Administering and Running Applications in lx Branded Zones (Tasks)
In general, a patch consists of the following components:
Patch information:
Identification, which is the patch version and patch ID
Applicability, which is the operating system type, operating system version, and architecture
Dependencies, such as requires and obsoletes
Properties, such as requires a reboot afterwards
One or more packages to patch, where each package contains:
The version of the package to which the patches can be applied
Patch information, such as ID, obsoletes, and requires
One or more components of the package to be patched
When the patchadd command is used to apply a patch, the patch information is used to determine whether the patch is applicable to the currently running system. If determined to be not applicable, the patch is not applied. Patch dependencies are also checked against all of the zones on the system. If any required dependencies are not met, the patch is not applied. This could include the case in which a later version of the patch is already installed.
Each package contained in the patch is checked. If the package is not installed on any zone, then the package is bypassed and not patched.
If all dependencies are satisfied, all packages in the patch that are installed on any zone are used to patch the system. The package and patch databases are also updated.
Note - Oracle Solaris 10 3/05 through Oracle Solaris 10 11/06: If a package is installed with pkgadd -G or has the pkginfo setting SUNW_PKG_THISZONE=true, the package can only be patched with patchadd -G. This restriction is removed in the Oracle Solaris 8/07 release.