Bug 120142
Summary: | 3.2.0 doc addition, section 1.7, point out that on new versions rhn_register is a symlink to up2date | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Patrick C. F. Ernzer <pcfe> |
Component: | Documentation | Assignee: | Clay Murphy <cmurphy> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fanny Augustin <fmoquete> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | rhn-bugs |
Target Milestone: | --- | Keywords: | Documentation, FutureFeature |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | rhn3.3 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-14 18:27:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 119397 |
Description
Patrick C. F. Ernzer
2004-04-06 12:08:14 UTC
the comment also applies to section 6.1 Configuring the Red Hat Network Registration client Yeah, I tried to address this in the chapters and sections specifically describing up2date and rhn_register (see the Warning at the beginning of chapters 2 and 6 and the first paragraph of section 2.2. Registration for examples) but this really should be brought up at the first reference to the tools, in this case, the section you mention. While I'm doing this, I'll also remove references to old, deprecated RHL versions and add a mention of RHEL 3. Accepting, aligning to the next (3.3.0) release, marking customer facing, and blocking the 330 doc tracking bug. Alrighty, I've explained fully in this section that RHEL 2.1 users need to use rhn_register but RHEL 3 customers have registration functionality built into up2date. Perhaps more importantly, I've used this task as a springboard to remove all references to RHL systems, as the last (RHL 9) is reaching its end of life before the next RHN release. This affected all of the Notes and Warnings describing the rhn_register requirement for older distributions scattered throughout the RHUA and RHNRC client chapters, as well as other areas. In fact, no RHL references should now exist in the reference guide whatsoever. Done a long time ago. Closing. |