patch Profile Keyword
patch patch_id_list | patch_file patch_location optional_keywords] |
- patch_id_list
-
Specifies the patch ID numbers that are to be installed. The list should be a list of comma-separated Solaris patch IDs. The patches are installed in the order specified in the list. Do not add a space after the comma, for example: 112467-01,112765-02.
- patch_file
-
A file with a list of patches that is found in the patch_location. The patches are installed in the order specified in the file.
- patch_location
-
Specifies the location where the patches reside. The locations allowed are the following:
-
NFS server
-
HTTP server
-
Local device
-
Local file
-
- optional_keywords
-
Optional keywords depend on where patches are stored. The following sections describe the possible locations and optional keywords.
Patches Stored on an NFS Server
If the patch is stored on an NFS server, use one of the following syntaxes for the patch keyword.
patch patch_id_list | patch_file nfs server_name:/patch_directory [retry n] patch patch_id_list | patch_file nfs://server_name/patch_director [retry n] |
- patch_id_list
-
Specifies the patch ID numbers that are to be installed. The list should be a list of comma-separated Solaris patch IDs. The patches are installed in the order specified in the list.
- patch_file
-
A file with a list of patches that is found in the patch_location. The patches are installed in the order specified in the file.
- server_name
-
Specifies the name of the server where you stored the patches.
- patch_directory
-
Specifies the location of the patch directory on the specified server. The patches must be in standard patch format.
- retry n
-
Is an optional keyword. n is the maximum number of times the install utility attempts to mount the directory.
Example 8–18 Adding a Patch With an Ordered List by Using NFS
In this example, the patch profile keyword adds all the patches listed in the patch file from the NFS patch directory nfs://patch_master/Solaris/v10/patches. Patches are installed in the order listed in the patch. If a mount fails, the NFS mount is tried five times.
patch patch_file nfs://patch_master/Solaris/v10/patches retry 5
Example 8–19 Adding a Patch by Using NFS
In this example, the patch profile keyword adds the patches 112467–01 and 112765–02 from the patch directory /Solaris/v10/patches on the server patch_master.
patch 112467-01,112765-02 nfs patch_master:/Solaris/v10/patches
Patches Stored on an HTTP Server
If the patch is stored on an HTTP server, use one of the following syntaxes for the patch keyword.
patch patch_id_list | patch_file http://server_name [:port] patch_directory optional_http_keywords |
patch patch_id_list | patch_file http server_name [:port] patch_directory optional_http_keywords |
- patch_id_list
-
Specifies the patch ID numbers that are to be installed. The list should be a list of comma-separated Solaris patch IDs. The patches are installed in the order specified in the list. Do not add a space after the comma, for example: 112467-01,112765-02.
- patch_file
-
A file with a list of patches that is found in the patch_location. The patches are installed in the order specified in the file.
- server_name
-
Specifies the name of the server where you stored the patch.
- port
-
Specifies an optional port. port can be a port number or the name of a TCP service that has a port number that is determined at runtime.
If you do not specify a port, the default HTTP port number 80 is used.
- patch_directory
-
Specifies the location of the patch directory to be retrieved from the specified server. When using an HTTP server, the patch must be in JAR format.
- optional_keywords
-
Specifies the optional keywords to use when you retrieve a patch from an HTTP server.
|
Keyword |
Value Definition |
|---|---|
|
timeout min |
The timeout keyword enables you to specify, in minutes, the maximum length of time that is allowed to pass without receipt of data from the HTTP server. If a timeout occurs, the connection is closed, reopened, and resumed. If you specify a timeout value of 0 (zero), the connection is not reopened. If a timeout reconnection occurs, the package is retried from the beginning of the package and the data that was retrieved prior to the timeout is discarded. |
|
proxy host:port |
The proxy keyword enables you to specify a proxy host and proxy port. You can use a proxy host to retrieve a Solaris package from the other side of a firewall. You must supply a proxy port when you specify the proxy keyword. |
Example 8–20 Adding a Patch With an Ordered List by Using HTTP
In this example, the patch profile keyword adds all the patches listed in the patch_file file from the HTTP location http://patch.central/Solaris/v10/patches. The patches are installed in the order specified in the file the patch file. If five minutes pass and no data is received, the patch data is retrieved again. Previous patch data is discarded.
patch patch_file http://patch.central/Solaris/v10/patches timeout 5
Example 8–21 Adding a Patch by Using HTTP
In this example, the patch profile keyword entry adds the patches 112467–01 and 112765–02 from the patch location http://patch_master/Solaris/v10/patches.
patch 112467-01,112765-02 http://patch.central/Solaris/v10/patches
Patches Stored on a Local Device
You can retrieve a Solaris package from a local device if you stored the package on a file system-oriented, random-access device, such as a diskette or a DVD-ROM. Use the following syntax for the patch keyword.
patch patch_id_list | patch_file local_device \ device path file_system_type |
- patch_id_list
-
Specifies the patch ID numbers that are to be installed. The list should be a list of comma-separated Solaris patch IDs. The patches are installed in the order specified in the list. Do not add a space after the comma, for example: 112467-01,112765-02.
- patch_file
-
A file with a list of patches that is found in the patch_location. The patches are installed in the order specified in the file.
- device
-
Specifies the name of the drive where the Solaris package resides. If the device name is a canonical path, the device is mounted directly. If you supply a device name that is not a canonical path, the installation utility adds /dev/dsk/ to the path.
- path
-
Specifies the path to the Solaris patch, relative to the root (/) file system on the device you specified.
- file_system_type
-
Specifies the type of file system on the device. If you do not supply a file system type, the installation utility attempts to mount a UFS file system. If the UFS mount fails, the installation utility attempts to mount an HSFS file system.
Example 8–22 Adding a Patch With an Ordered List by Using a Local Device
In this example, the patch profile keyword adds all the patches listed in the patch_file file from the directory /Solaris_10/patches from the local device c0t6d0s0. The patch file determines the order of patches to be installed.
patch patch_file c0t6d0s0 /Solaris_10/patches
Example 8–23 Adding a Patch by Using a Local Device
In this example, the patch profile keyword adds the patches 112467–01 and 112765–02 from the patch directory /Solaris_10/patches from local device c0t6d0s0.
patch 112467-01,112765-02 local_device c0t6d0s0 /Solaris_10/patches
Patches Stored on a Local File
A patch can be installed from the miniroot from which you booted the system. When you perform a custom JumpStart installation, you boot the system from a DVD, CD, or an NFS-based miniroot. The installation software is loaded and run from this miniroot. Therefore, a patch that you stored in the DVD, CD, or NFS-based miniroot is accessible as a local file. Use the following syntax for the patch keyword.
patch patch_id_list | patch_file local_file patch _directory
- patch_id_list
-
Specifies the patch ID numbers that are to be installed. The list should be a list of comma-separated Solaris patch IDs. The patches are installed in the order specified in the list. Do not add a space after the comma, for example: 112467-01,112765-02.
- patch_file
-
A file with a list of patches that is found in the patch_location. The patches are installed in the order specified in the file.
- patch_directory
-
Specifies the location of the patch directory. The patch directory must be accessible to the system as a local file while the system is booted from the Solaris Software - 1 CD or from the Solaris Operating System DVD. The system cannot access /net when it is booted from the Solaris Software - 1 CD or from the Solaris Operating System DVD.
Example 8–24 Adding a Patch With an Ordered List by Using a Local File
In this example, the patch profile keyword adds all the patches that are listed in the patch_file file from the /Solaris_10/patches directory. The patch file determines the order of patches to be installed.
patch patch_cal_file /Solaris_10/patches
Example 8–25 Adding a Patch by Using a Local File
In this example, the patch profile keyword adds the patches 112467–01 and 112765–02 from the patch directory /Solaris_10/patches.
patch 112467-01,112765-02 local_file /Solaris_10/patches
Limitations When Using the patch Keyword
Note the following limitations when using the patch keyword:
-
Patches cannot be retrieved from FTP locations or local backup, such as tape.
-
Signed patches cannot be added.
-
Patches must be installable with the patchadd command.
-
If a patch depends on a patch that is not currently installed, the patch is not installed. An error message is logged into the installation or upgrade log file.
-
You must determine the correct order of the patches for a correct installation of the patches.
- © 2010, Oracle Corporation and/or its affiliates