Bug 160906 - To force file system integrity check, rc.sysinit should accept 'any key' instead of just 'Y'
To force file system integrity check, rc.sysinit should accept 'any key' ins...
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: initscripts (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2005-06-18 06:34 EDT by David Tonhofer
Modified: 2014-03-16 22:54 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-20 12:44:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Tonhofer 2005-06-18 06:34:46 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4

Description of problem:
On boot, rc.sysinit  may  ask you to 

"Press Y within %d seconds to force file system integrity check..."

However, as the keyboard mapping may not yet be correct at that point,
pressing 'Y' often means pressing 'Y', cussing, hunting and pressing 'Z'
at which time the %d seconds may already have passed.

It would be easier on the Sysop's heart rate if the message was

"Press any key within %d seconds to force file system integrity check..."

with any extant key presses flushed from the buffer first of course.

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

How reproducible:

Steps to Reproduce:

Actual Results:  n/a

Expected Results:  n/a

Additional info:

Comment 1 Bill Nottingham 2005-06-20 12:44:23 EDT
Loadkeys is already done at that point, so if the keymapping is *still*
incorrect; that implies a different problem; I'm not sure changing the config to
deal with an invalid config is worth it.
Comment 2 David Tonhofer 2005-06-20 13:43:22 EDT
Uh-huh. However, we are talking multi-language environment here:
i.e. we are using three different types of keyboards in the office.
Now, if someone decides to go down to the "server inn" to do a little
intervention and takes his keyboard along, there is bound to be
some confusion.

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