Description of problem:
Install RHEL6 B2 on encrypted volume.
On boot the systems prompts for a password - but provides no hint what the password is for.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install on encrypted volume
3. prompted for password
no hints on what the password is for.
hints on what the passowrd is for.
Useful if different volumes have different passwords.
So the issue here is we don't have access to fonts, translations, etc until the root filesystem is mounted.
It's not a problem in practice, though, because in most circumstanced we only need to know one thing before mounting the root filesystem. Namely, we need to know the password to mount the root filesystem with.
Since it's only one thing, and the user already knows he/she will need to enter it to continue, conveying "nows the time to type your password" is all we need to do. We accomplish this with a "lock icon" and a text entry field on screen.
We could potentially change the lock icon to a hard drive icon with a lock emblem or some such. That would make it even clearer it's a "hard drive password" and not just a password.
This missed the non-blocker deadline, proposing for 6.1
ack if I can get suitable artwork
Created attachment 468724 [details]
encrypted drive icon suitable for the purpose
SVG included as source, not intended for installation
Created attachment 483701 [details]
old vs. new icon comparison
New drive icon from comment 9 is present in plymouth-0.8.3-22.el6.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Previously, the system prompted for a password on boot but provided no hint as to what the password was for. That caused unnecessary confusion for some users, who didn't know which of their passwords to enter. With this update, a hard drive icon has been added to prompts associated with encrypted disk volumes and the password prompts for encrypted disks are now easy to recognize.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.