Bug 12221 – bootnet/boot: slightly different behaviour in keyboard layout selection

Bug 12221 - bootnet/boot: slightly different behaviour in keyboard layout selection

Summary:	bootnet/boot: slightly different behaviour in keyboard layout selection

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	installer (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	i386 Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Matt Wilson
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:	Florence Gold
Keywords:

Depends On:
Blocks:	13068
	Show dependency tree / graph

Reported:	2000-06-13 16:21 EDT by Pekka Savola
Modified:	2005-10-31 17:00 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2001-03-02 12:43:17 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Pekka Savola 2000-06-13 16:21:06 EDT

Using the latest updates disk and the latest boot.img/bootnet.img 
(CDROM/FTP Server).

Beginning the installation with 'text updates'.

In keyboard layout selection menu, pressing 'F' yields different 
selection in bootnet/boot.  The one goes to 'fi', the other to 'fi-latin1'.
Both layouts still exist in both cases, the hotkey algorithm just seems to 
be different (or one layout is missing from one).

Comment 1 Brock Organ 2000-06-13 18:06:56 EDT

verified ... the inconsistency occurs in selecting the keyboard in stage1 (ie
bootnet.img w/fi-latin1 as first "f" key entry) vs selecting the keyboard in
stage2 (boot.img w/CDROM w/fi as first "f"  key entry) ...

Comment 2 Matt Wilson 2000-06-16 11:13:44 EDT

very minor, remind me for next release.

Comment 3 Pekka Savola 2000-10-23 15:30:58 EDT

This has been fixed in 7.0 (text mode).  I've had some reports that this might have been
broken in graphical install -- haven't checked that out myself.

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