Bug 1129723

Summary: RFE: Help for every spoke in text mode
Product: Red Hat Enterprise Linux 7 Reporter: Tomas Capek <tcapek>
Component: anacondaAssignee: Vratislav Podzimek <vpodzime>
Status: CLOSED WONTFIX QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: mbanas, mkolman, release-test-team-automation
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1072033 Environment:
Last Closed: 2014-08-13 15:15:45 UTC Type: Bug
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: 1072033, 1147518    
Bug Blocks:    

Description Tomas Capek 2014-08-13 14:26:27 UTC
+++ 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.

Comment 2 Chris Lumens 2014-08-13 14:56:25 UTC
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.

Comment 3 RHEL Program Management 2014-08-13 15:15:45 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.