Use this task map to identify all the tasks for managing patches in the Solaris environment. Each task points to a series of additional tasks such as managing signed or unsigned patches.
Task |
Description |
For Instructions |
---|---|---|
Identify disk space requirements for patches |
Identify whether your system has enough disk space to download or spool patches. | |
Determine if adding signed or unsigned patches |
Determine whether adding signed or unsigned patches is best for your environment. | |
Add a signed or unsigned patch to your system |
Select one of the following: |
|
|
Add a signed patch to a your system. | |
|
Add an unsigned patch to your system. |
Keep the following disk space considerations in mind before you begin downloading or spooling patches:
The default download directory for signed patches is /var/sadm/spool. Unsigned patches that are spooled are also stored in /var/sadm/spool.
The patch download process might use more disk space than anticipated because multiple patches can be downloaded, if prerequisite patches are required by the patch that you downloaded.
Signed patches are unpacked in the /var/sadm/spool directory before they are installed. Be sure you have enough disk space in the /var directory for this process.
If your /var directory is not large enough to support the downloading and unpacking of signed patches, you can use the smpatch command with the -d option to specify an alternate patch download directory.
You can safely remove the patches from the /var/sadm/spool directory after they are successfully downloaded and added to your system to reclaim disk space in the /var directory.
The key factor in determining when to add signed or unsigned patches is whether or not the secure download of patches is important in your environment. If the secure download of patches is important in your environment, then add signed patches to your system.