On Fri, 2011-11-18 at 17:05 -0800, John Reiser wrote: > >> 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. I may have been unclear here - what I'm concerned about is whether we need *user-facing* interactive elements. Diagnosing and debugging problems is a *developer* problem, generally. We can easily have a nice (English) error messages and bash/readline interactive UI for error recovery - with the default (us) keymap[1]. I have no problem with this stuff. On the other hand, I feel we have a responsibility to properly translate and localize *user-facing* UI elements. Which requires us to have further UI to pick the language and keymap. Most install cases (CD, DVD, Live USB, etc). will not require any user-facing UI in initramfs - they'll immediately load stage2 and be merrily on their way. PXE and other netboot scenarios should do the same, unless the server is misconfigured[2]. Basically: I understand that you, as a developer, want interactive debuggability. That's cool, I want that too. But do we really expect normal users to have to deal with unrecoverable errors (e.g. misconfigured netboot servers) *so often* that we should write an entirely new language/keymap picker just for that? I'm not so sure. -w [1] This seems to be accepted practice for Linux development - the bootup messages, for instance, are all in English. No translations. [2] Also note that configuring a PXE server can be done on a system that will have the proper local language/keymap, using translated documentation. _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
