Appendix A starts with the advice For more information about re-installing your Red Hat Enterprise Linux system, refer to the Technical Whitepapers available online at http://www.redhat.com/docs/wp/. If I click on the link, I'm at the Whitepapers home page, with no clue how to get to one relevant to this topic. I tried typing "re-installing" into the Keyword search box and got 5 hits, none of which was even part of the Whitepapers. They were all parts of manuals for RH 7.0, 6.0, and 5.2 (!). Ok, perhaps that was just a "FYI" reference that can be safely ignored. But then on the next page, I get another reference which seems more important: To re-install your system, select Perform a new Red Hat Enterprise Linux installation and refer to http://www.redhat.com/docs/wp/ as well as Chapter 4 Installing Red Hat Enterprise Linux for further instructions. I've found similar useless cross-refernces elsewhere in the documentation. I can understand not using a direct URL to the document in question because URLs tend to change over time, but a least you need to give some assistence in navigating to the document in question.
Re-assigning to current Installation Guide owner.
Removing automation notification
Moving to Don
removed reference to "http://www.redhat.com/docs/wp/", which is the only fix i can do as per this bug. this should help prevent confusion among users, since the next paragraph instructs users to refer to another chapter within the book (i.e. "Installing RHEL". setting this bug as MODIFIED.
The reference to the whitepapers page still exists here: http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/en-US/rhel-ig-x8664-multi-en-4/s1-upgd-migrate.html but the link is a bit different and does not work.
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.