Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 479941[details]
Suggested changes and updates.
I went through Installation Guide (Edition 1.0) and came up with suggestions for update in attached file. The wording needs some work, sometimes I only basically describe what is happening. The screenshots I refer to in the document are only informative, their theme doesn't fit the one used in the guide.
To update the attachment from description:
> - 28.1.5. Manually Configuring the Network Settings
>
> Also network device selection dialog (screenshot [3]) which appears
> before the "Configure TCP/IP" screen in case of more NICs present
> (there may be some automatic selection like ibft device preferred
> automatically, we are investigating how it works exactly to provide
> description), and corresponding ksdevice boot option could be mentioned.
Indeed, the only automatic device selection (in case of missing ksdevice= boot option) should happen when ibft device with link is detected.
Created attachment 481862[details]
update of network kickstart command
The attachment contains update on kickstart network command. It is a patch of the document from the first attachment.
Comment 4Ruediger Landmann
2011-04-19 18:16:29 UTC
*** Bug 681843 has been marked as a duplicate of this bug. ***
Comment 5Ruediger Landmann
2011-05-09 09:10:33 UTC
Thanks Radek; all issues addressed in build 1.0-37
Note to QE: This is probably best checked against the html-single version of the doc. Radek's attachments include the multiple specific sections and subsections to which his comments apply. These numbers remain unchanged in the current build, so searching for them should confirm his suggested changes in place in every case.
Created attachment 479941 [details] Suggested changes and updates. I went through Installation Guide (Edition 1.0) and came up with suggestions for update in attached file. The wording needs some work, sometimes I only basically describe what is happening. The screenshots I refer to in the document are only informative, their theme doesn't fit the one used in the guide.