Bug 56379 - RFE: kickstart does use non us keyboard map if input is needed
Summary: RFE: kickstart does use non us keyboard map if input is needed
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-11-16 15:46 UTC by Anne Possoz
Modified: 2007-04-18 16:38 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-11-16 15:51:18 UTC
Embargoed:


Attachments (Terms of Use)

Description Anne Possoz 2001-11-16 15:46:50 UTC
Description of Problem:

While in kickstart installation, the keyboard in always "us" and this
makes it difficult if we have to act in screen 2, for example, or
enter any info interactively.
As this is not the case in manual install, I assume that anaconda, while
using kickstart method, doesn't take into account parameters during the
install itself but just transmit it to the installed configuration.
And effectively, the keyboard is well configured after kickstart
installation.

My ks.cfg file contains:
keyboard fr_CH-latin1


Version-Release number of selected component (if applicable):


How Reproducible:
All versions of kickstart, at least up to redhat 7.1

Steps to Reproduce:
1. keyboard fr_CH-latin1 (in ks.cfg)
2. while installation proceed, go to screen 2
   and type <shift>7boot (that should be /boot)
   On s fr_CH-latin1 keyboard, we have to type -boot
   (same for so many keys on keyboard)
3. try the same in manual installation

Actual Results:


Expected Results:


Additional Information:

Comment 1 Jeremy Katz 2001-11-26 20:07:54 UTC
Fixed in CVS


Note You need to log in before you can comment on or make changes to this bug.