>> 1) Driver update disks require an interactive element at boot time.
[snip]
> Why do they require an interactive element? What input is needed? Device
> name? Filename?
For me, the interactive element is for diagnosis and recovery from errors.
First, I want really good error messages: ones that are good enough
to help you _fix_ the problem. For example, not just "No such file or directory"
but "Looking for foobar configuration file; cannot open /path/to/the/missing/file
because directory /path/to/the/missing does not exist."
Then, I want the "last input" loaded into the line editor, with the cursor
positioned appropriately, and so that activating the line re-starts the
part that failed ("Looking for foobar configuration file" with new pathname),
except that <ESC> backs up one step farther, etc.
The convenience of retrying the failing action (or backing up step by step)
without having to start over from the very beginning, and receiving help
such as pre-loading the line editor, is worth a lot for Usability.
Being unable to proceed (except by re-booting) is a symptom of failure
in the UI.
--
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
