180
Chapter 8. UNIX Support Guide
ing systems use Errata Updates to associate upgrades with specific packages. In addition,
Solaris uses answer files to automate interactive package installations, something Linux
doesn’t understand, while Red Hat offers the concept of source packages. For this reason,
this section seeks to highlight differences in using RHN tools on UNIX systems. (Note:
RHN does not support Solaris answer files in the current release; such support is planned
for future releases.)
8.4.2.1. Updating Through the Website
Despite inherent differences, such as the lack of Errata, the channel and package manage-
ment interfaces within the RHN website on the Satellite work largely the same for UNIX
systems. All software channels designed to serve UNIX variants can be constructed almost
exactly as the custom channels described in the
RHN Channel Management Guide
. The
most significant difference is the architecture. When creating a UNIX software channel,
ensure you select the base channel architecture appropriate for the systems to be served.
Furthermore, Red Hat recommends you break down your packages into base and child
channels depending on their nature. For example, on Solaris, installation packages should
go in the Solaris base channel, while patches and Patch Clusters should go in a child chan-
nel of the Solaris base channel. Extra installation packages can go in a separate Extras child
channel.
RHN treats patches similarly to packages; they are listed and installed in the same way and
with the same interface as normal packages. Patches are ’numbered’ by Solaris, and will
have names like "patch-solaris-108434". The version of a Solaris patch is extracted from
the original Solaris metadata, and the release is always 1.
Patch Clusters are bundles of patches that are installed as a unit. RHN keeps track of
the last time that a Patch Cluster was installed successfully on a system. However, Patch
Clusters are not tracked on the client as installed entities so they do not appear in the
installed packages or patches list. Patch Cluster names look like "patch-cluster-solaris-
7_Recommended". The version is a datestring, such as "20040206", the release is always
1 and the epoch is always 0.
To install packages or patches on an individual system, click the name of the system in the
Systems
category, select the packages from the Upgrade or Install lists of the
Packages
or
Patches
tab, and click
Install/Upgrade Selected Packages
.
To run a remote command while installing the package, click
Run Remote Command
rather than
Confirm
. Refer to Section 8.5
Remote Commands
for instructions.
To install packages or patches on multiple systems at once, select the systems and click
System Set Manager
in the left navigation bar. Then, in the
Packages
tab, select the pack-
ages from the Upgrade or Install lists and click
Install/Upgrade Packages
. To complete
the action, schedule the updates.
Содержание NETWORK 4.0 -
Страница 1: ...Red Hat Network 4 0 Reference Guide...
Страница 10: ......
Страница 16: ...vi Introduction to the Guide...
Страница 24: ...8 Chapter 1 Red Hat Network Overview...
Страница 40: ...24 Chapter 2 Red Hat Update Agent Figure 2 11 Available Package Updates...
Страница 58: ...42 Chapter 2 Red Hat Update Agent...
Страница 80: ...64 Chapter 5 Red Hat Network Registration Client Figure 5 15 Text Mode Welcome Screen...
Страница 186: ...170 Chapter 7 Monitoring...
Страница 200: ...184 Chapter 8 UNIX Support Guide...
Страница 214: ...198 Appendix A Command Line Config Management Tools...
Страница 274: ...258 Appendix C Probes...
Страница 282: ...266 Glossary...