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.

+++ This bug was initially created as a clone of Bug #1072033 +++

Help in anaconda is currently non-existent.

Only the manual partitioning screen contains some help, which is not formatted, contains typos, and is somewhat outdated (for example, "Apply changes" is now "Update Settings").

With the adequate documentation in the Installation Guide, we can have relevant help for every spoke.


This RFE is to provide a new option in text mode for each spoke. Upon selecting the option, an appropriate help from the IG for the current spoke should appear, using the less utility.

This isn't really appropriate for text mode, though.  First, if we just use the installation guide text, it's going to have to be completely reformatted for a text interface, which means now we are starting to have to maintain our own copy of the documentation, or at least our own rules for how to convert it.  Second, displaying this on a text interface is going to require a pager and it's going to involve scrolling off the interface the user was working with.  In other words, the user won't be able to see the documentation and the thing it is documenting at the same time.  Finally, the text interface is not and will never be a complete copy of the GUI, and we should not try to make it that way.  It is a more limited environment and is not the primary interface to anaconda.  If the user needs more advanced capabilities, they need to use a more advanced interface.

I think this is a bad idea, and could not object to its inclusion more.

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.