Bug 74084 - Incorrect keytables directory in RH Reference Guide
Summary: Incorrect keytables directory in RH Reference Guide
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rhl-rg
Version: 7.3
Hardware: noarch
OS: Linux
low
low
Target Milestone: ---
Assignee: Johnray Fuller
QA Contact:
URL: http://www.redhat.com/docs/manuals/li...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-09-15 13:14 UTC by Brett Dufault
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-09-16 15:16:00 UTC
Embargoed:


Attachments (Terms of Use)

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


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