use libexecdir, bindir, sbindir, switch to /usr/lib/udev in documentation

[elogind.git] / extras / keymap / README.keymap.txt

diff --git a/extras/keymap/README.keymap.txt b/extras/keymap/README.keymap.txt
index 9c2d5dc16a151d57720b1dfe39e784f1b1d47367..acdc00283a0e0aa866140f2706323f3faa3a2b46 100644 (file)
--- a/extras/keymap/README.keymap.txt
+++ b/extras/keymap/README.keymap.txt
@@ -44,20 +44,16 @@ for inclusion you need to do the following steps:
 
  1. Find the keyboard device.
 
- Run /lib/udev/findkeyboards. This should always give you an "AT
+ Run /usr/lib/udev/findkeyboards. This should always give you an "AT
  keyboard" and possibly a "module". Some laptops (notably Thinkpads, Sonys, and
  Acers) have multimedia/function keys on a separate input device instead of the
  primary keyboard. The keyboard device should have a name like "input/event3".
  In the following commands, the name will be written as "input/eventX" (replace
  X with the appropriate number).
 
- 2. Dump current mapping:
+ 2. Find broken scan codes:
 
- sudo /lib/udev/keymap input/eventX > /tmp/orig-map.txt
-
- 3. Find broken scan codes:
-
- sudo /lib/udev/keymap -i input/eventX
+ sudo /usr/lib/udev/keymap -i input/eventX
 
  Press all multimedia/function keys and check if the key name that gets printed
  out is plausible. If it is unknown or wrong, write down the scan code (looks
@@ -71,30 +67,28 @@ for inclusion you need to do the following steps:
    0x1E www # Fn+F2 web browser
 
  Repeat that for all other keys. Write the resulting list into a file. Look at
- /lib/udev/keymaps/ for existing key map files and make sure that you use the
+ /usr/lib/udev/keymaps/ for existing key map files and make sure that you use the
  same structure.
 
  If the key only ever works once and then your keyboard (or the entire desktop)
  gets stuck for a long time, then it is likely that the BIOS fails to send a
  corresponding "key release" event after the key press event. Please note down
  this case as well, as it can be worked around in
- /lib/udev/keymaps/95-keyboard-force-release.rules .
+ /usr/lib/udev/keymaps/95-keyboard-force-release.rules .
 
- 4. Find out your system vendor and product:
+ 3. Find out your system vendor and product:
 
  cat /sys/class/dmi/id/sys_vendor
  cat /sys/class/dmi/id/product_name
 
- 5. Generate a device dump with "udevadm info --export-db > /tmp/udev-db.txt".
-
- 6. Send the system vendor/product names, the key mapping from step 3,
- /tmp/orig-map.txt from step 2, and /tmp/udev-db.txt from step 5
- to the bug tracker, so that they can be included in the next release:
+ 4. Generate a device dump with "udevadm info --export-db > /tmp/udev-db.txt".
 
-   https://bugs.launchpad.net/udev/+bugs
+ 6. Send the system vendor/product names, the key mapping from step 2,
+ and /tmp/udev-db.txt from step 4 to the linux-hotplug@vger.kernel.org mailing
+ list, so that they can be included in the next release.
 
-For local testing, copy your map file to /lib/udev/keymaps/ with an appropriate
-name, and add an appropriate udev rule to /lib/udev/rules.d/95-keymap.rules:
+For local testing, copy your map file to /usr/lib/udev/keymaps/ with an appropriate
+name, and add an appropriate udev rule to /usr/lib/udev/rules.d/95-keymap.rules:
 
   * If you selected an "AT keyboard", add the rule to the section after
   'LABEL="keyboard_vendorcheck"'.