Bug 74084

Summary: Incorrect keytables directory in RH Reference Guide
Product: [Retired] Red Hat Linux Reporter: Brett Dufault <brettzilla>
Component: rhl-rgAssignee: Johnray Fuller <jrfuller>
Status: CLOSED ERRATA QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: noarch   
OS: Linux   
URL: http://www.redhat.com/docs/manuals/linux/RHL-7.2-Manual/ref-guide/s1-boot-init-shutdown-sysconfig.html
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-09-16 15:16:00 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 Brett Dufault 2002-09-15 13:14:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020509

Description of problem:
The /etc/sysconfig/keyboard section in the Reference Guide indicates that
keytables are under /usr/lib/keymaps/i386.  The files are actually under
/lib/keymaps/i386.  Users following the Ref Guide instructions may incorrectly
believe that they are missing the keytables.

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


How reproducible:
Always

Steps to Reproduce:
1. Read keyboard section of Reference Guide's Sysconfig chapter (see URL)
2. ls /usr/lib/kbd/keymaps/i386
3. ls /lib/kbd/keymaps/i386

Actual Results:  /usr/lib/kbd/keymaps/i386 - no such directory
/lib/kbd/keymaps/i386 - contains keytable directories


Expected Results:  Ref Guide should remove "/usr" from the two directory
references in the KEYTABLE section -- files are under /lib/kbd/..., not
/usr/lib/kbd...

Additional info:

Comment 1 Johnray Fuller 2002-09-16 15:15:52 UTC
Good catch!

I am not sure how long that path has been in the docs, so I'll investigate and
put a docs errata out. I will close the bug when it is done.

J

Comment 2 Johnray Fuller 2002-10-15 23:00:59 UTC
This came in too late to effect the 8.0 release cycle, so I have posted an
errata for both 7.3 and 8.0 as well as correcting the source for posterity :-)

Thank you for catching this and taking the time to report it.

Johnray