Chapter 1. Introduction


This document explains how Red Hat Satellite 6 can support a rigid patching lifecycle for Red Hat Enterprise Linux systems.

This document explains how to perform in Satellite 6 patching procedures that are similar to the patching procedures defined in Rich Jerrido’s Red Hat Satellite 5.6 Errata Management Guide. In that guide, the command spacewalk-clone-by-date was the primary mechanism by which a patching schedule was defined. Satellite 6 has no such command and instead uses hammer. This guide explains how to use hammer to define a Content View that performs the same function as spacewalk-clone-by-date.

1.1. Audience

The audience for this guide is Systems and Security Administrators who are responsible for implementing a scalable and rigid patching schedule.

1.2. Requirements

Readers of this guide should be familiar with Red Hat Satellite and its terminology.

Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.