----- Original Message ---- > From: JM Ibanez <[EMAIL PROTECTED]> > To: [email protected] > Sent: Friday, December 14, 2007 3:46:35 PM > Subject: Re: [plug] Virtual Servers > > Michael Tinsay writes: > > > Yes I can. > > > > Unfortunately evdev can only handle /dev/input/event[0-9] in > > xorg.conf. Pointing evdev to something like > > /dev/input/by-path/InsertUSBAdddressHere is not possible (at least in > > Ubuntu Gutsy and all previous releases of Ubuntu -- I would > imagine > it > > would be the same for Debian). Even something like > > /dev/input/event-kbd[0-9] can't be handled. > > There are many ways to skin this particular cat. > > * You can pin the evdev driver to a particular device, if the devices > have different names via the "Name" option, as follows: > > Option "Name" "SynPS/2 Synaptics TouchPad"
I have three keyboards of the same brand/model. ;-) I have to rely on their physical device address. > > The value here is what's in the name field > in > /proc/bus/input/devices > > * You can pin the evdev device nodes that udev generates (for > event[0-9]). See http://reactivated.net/writing_udev_rules.html for > some help on writing udev rules. >From what I have read, udev cannot override kernel-assigned names, like >event[0-9] -- I tried with no luck. Udev can only give them additional names >or symlinks, but the original kernel name is preserved. > > * You can use something other than evdev. Like? Driver "kbd" + [Option "Device" "/dev/input/xxx" | Option "Dev Phys" "physical address"] does not work. I haven't found anything else. --- mike t. _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
