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: DocumentationAssignee: Clay Murphy <cmurphy>
Status: CLOSED CURRENTRELEASE QA Contact: Fanny Augustin <fmoquete>
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: 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
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040124

Description of problem:
We should point out that newer versions of up2date actually include
rhn_register

Version-Release number of selected component (if applicable):
RHNpro(EN)-3.2-Print-RHI(2004-03-16T17:59)

Actual Results:  we do explain the old rhn_register but fail to
explain that (on RHEL 3 for example) we now have rhn_register
functionality in up2date and that the former is only a symlink to the
latter.

Expected Results: Explain the above and also explain that on first use
up2date will act like it was called as 'up2date --register'

Additional info:

I do not know at which version we started this, up2date-4.2.5-1
includes the register functionality, in up2date-2.9.3-2.2.1AS there
still is a separate rhn_register-2.9.3-1.2.1AS

Comment 1 Patrick C. F. Ernzer 2004-04-06 16:04:03 UTC
the comment also applies to section 6.1 Configuring the Red Hat
Network Registration client

Comment 2 Clay Murphy 2004-04-13 22:30:43 UTC
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.

Comment 3 Clay Murphy 2004-04-17 00:23:43 UTC
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.

Comment 4 Todd Warner 2005-09-14 18:27:26 UTC
Done a long time ago. Closing.