![Silicon Graphics Prism User Manual Download Page 169](http://html.mh-extra.com/html/silicon-graphics/prism/prism_user-manual_1271592169.webp)
Customizing the XF86Config File
007-4701-003
147
Identifying Event Devices
An “event device” is a keyboard or pointing device. All event devices connected to the
system are listed at boot time on lines beginning with the string “input.” These boot
messages may be displayed at a Linux command prompt using the
dmesg
command.
The output from the
dmesg
command can be quite long, and therefore is usually filtered
with a
grep
command. For example:
# dmesg | grep ^input
input0: USB HID v1.10 Keyboard [NOVATEK Generic USB Keyboard] on usb1:4.0
input1: USB HID v1.00 Mouse [Logitech N43] on usb1:5.0
input2: USB HID v1.00 Mouse [Logitech N43] on usb1:6.0
input3: USB HID v1.10 Keyboard [NOVATEK Generic USB Keyboard] on usb1:7.0
input4: USB HID v1.00 Keyboard [SILITEK USB Keyboard and Mouse] on usb1:9.0
input5: USB HID v1.00 Mouse [SILITEK USB Keyboard and Mouse] on usb1:9.1
input6: USB HID v1.00 Mouse [Logitech N43] on usb1:10.0
All input devices detected during boot-up will have device nodes created for them in the
/dev/input
directory as follows:
•
Each keyboard will have an associated event* device node.
•
Each pointing device will have both an associated event* device node and an
associated mouse* device node.
The mapping of devices to nodes is by number (that is, input0 maps to event0, input1
maps to event1, and so on). The first input that is a pointing device gets mapped to
mouse0, the next input that is a pointing device gets mapped to mouse1, and so on.
The
dmesg
output shown above would therefore create the following mapping:
input0: event0
input1: event1, mouse0
input2: event2, mouse1
input3: event3
input4: event4
input5: event5, mouse2
input6: event6, mouse3
This mapping can then be used to edit the XF86Config-Nserver file, as described in the
next subsection, “Creating a Multi-Seat XF86Config File” on page 148.