Bug 2494

Summary:	Keytable setting and mounting are done in wrong order.
Product:	[Retired] Red Hat Linux	Reporter:	jtiisto
Component:	initscripts	Assignee:	David Lawrence <dkl>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0	CC:	jtiisto
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	1999-05-03 15:05:33 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description jtiisto 1999-05-03 06:56:02 UTC

If you have a different /usr partition rc.sysinit fails to
set the correct keymap since the keymaps and layouts are in
/usr and it's mounted after the setting of the keymap.

Comment 1 Bill Nottingham 1999-05-03 15:05:59 UTC

yes, but the keymap will still be loaded by the keytable initscript
later in the boot process, just as it was in 5.2. The loading
in rc.sysinit is for people that put the keymap in
/etc/sysconfig/console, so that they have the keymap loaded
if they need to login (fsck problems, etc.)