[Previous] [Contents] [Index] [Next]


Detect input devices and start the input manager


inputtrap [-f device] [-l device] [-s] 
          [-T] [-t trapfile] [-V...] 
          [-v[v]...] [-X class]... [-x device]... 
          [start] [query]


-f device
Probe for device first.
-l device
("el") Probe for device last.
Safe mode (probe only for a keyboard).
Ignore the trapfile, if present.
-t trapfile
Specify an alternative trapfile.
Pass a -v to devi-hirun.
Verbose output. More v characters cause more verbosity.
-X class
Exclude any devices of class from scan.
-x device
Exclude device from scan.
Start the driver. Once one input device from each class of device is recognized, inputtrap starts the driver for the first device found in each class.
Probe for input devices. If query is specified, inputtrap gives a printout of the command line required to start devi-hirun.


The inputtrap utility starts the input manager. It runs in one of the following ways:


If probing, inputtrap probes for input devices, and writes to stdout the invocation commands along with the appropriate options and arguments for starting the found devices.

The probing order is as follows:

  1. Keyboard (kbd)
  2. PS/2 mouse (ps2)
  3. fd-connected relative-coordinate pointing devices (fd) , conforming to the COM Plug and Play standard.

The device names (given above) are recognized as arguments to the -f and -x options.

Using a trapfile

To override the options that inputtrap uses by default, probe the devices as described above, redirect the output to a file, and then edit the file. When the options are correct, move or copy the trapfile to /etc/system/trap/input.${HOSTNAME}.

If a /etc/system/trap/input.${HOSTNAME} file exists, inputtrap uses the contents of this file as arguments to start a devi-* driver.

Each line of the trapfile corresponds to a separate invocation of a devi-* driver. The first word on the line indicates the driver to start. For example:

devi-ahl ahl fd -d/dev/ser1

The above line tells inputtrap to start the AHL touchscreen driver.

If the line doesn't start with the name of a devi-* driver, inputtrap starts devi-hirun. For example:

kbd fd -d/dev/kbd ps2 k6-2


Check for input devices. Once one of each class of device has been recognized, spawn devi-hirun with an appropriate command line:


Caution: Adding invalid information to the input.hostname file can cause the system to hang. If your hardware changes, remember to remove the old input.hostname file.

See also:


Input drivers (devi-*) in the Utilities Summary

Connecting Hardware in the Neutrino User's Guide

[Previous] [Contents] [Index] [Next]