Using Automatic Updates with RHN Classic

Warning: Deprecate Feature

Automatic system updates are only available using RHN Classic, which basis subscription consumption on access to content repository channels. RHN Classic is available as a convenience for customer environments with legacy systems which have not updated to Certificate-Based CentOS Network.

The update and content stream is different for Certificate-Based CentOS Network, so automatic updates are not used.

The new Certificate-Based CentOS Network and the differences between Certificate-Based CentOS Network and RHN Classic are described in Product Subscriptions and Entitlements.

RHN Classic allows the majority of the update process to be automated. It determines which RPM packages are necessary for the system, downloads them from a secure repository, verifies the RPM signature to make sure they have not been tampered with, and updates them. The package install can occur immediately or can be scheduled during a certain time period.

RHN Classic requires a system profile for each machine, which contains hardware and software information about the system. This information is kept confidential and is not given to anyone else. It is only used to determine which errata updates are applicable to each system, and, without it, RHN Classic can not determine whether a given system needs updates. When a security errata (or any type of errata) is released, RHN Classic sends an email with a description of the errata as well as a list of systems which are affected. To apply the update, use the CentOS Update Agent or schedule the package to be updated through the RHN Classic Subscription Management area of the Customer Portal.

Before installing any security errata, be sure to read any special instructions contained in the errata report and execute them accordingly. Refer to "Applying the Changes" for general instructions about applying the changes made by an errata update.