Xorg now relies by default entirely on HAL for input device configuration,
and only uses xorg.conf entries for input devices if you disable that.
This is what the man page refers to in the first paragraph under
configuration details:
Depending on the X server version in use, input device
options may be set in either a xorg.conf file, or in the
configuration files read by the Hardware Abstraction Layer
(HAL) daemon, hald(1).
/etc/hal/fdi/preprobe/10osvendor/10-x11-input.fdi is the system-delivered
HAL/X11 input device configurations - but if you edit it directly, I don't
know if IPS will keep your changes or not on future image-updates, and am
not in a position to test that right now. I think you could copy that to
/etc/hal/fdi/policy/30user/ and strip it down to just overwriting/adding the
values you want to modify from the default. The lshal command will show
you the values hal is reporting for debugging.
The other alternative is to revert to the pre-HAL static configurations,
if you don't need multiple device support or support for starting with
no devices and then hotplugging them in later.
For that. see:
http://who-t.blogspot.com/2008/07/input-configuration-in-nutshell.html
(When reading that blog or other Xorg/HAL docs, remember that unlike linux,
we still use kbd, since our kernel doesn't support the evdev device
interfaces that Linux invented, but kbd on Solaris supports hotplugging and
HAL configuration.)
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
Edward Pilatowicz wrote:
> hey all,
>
> so i just image updated from b118 to b121. when running b118 i had the
> caps lock key on my keyboard remapped to behave as a ctrl key. this
> was done via the following entry in my xorg.conf file:
>
> ---8<---
> Section "InputDevice"
> Identifier "CoreKeyboard"
> Driver "kbd"
> Option "XkbOptions" "ctrl:nocaps"
> EndSection
> ---8<---
>
> but this no longer works with b121. the kbd.7 man page still makes a
> reference to XkbOptions, and looking at the /var/log/Xorg.0.log it seems
> that the kbd driver is still being loaded, but the configuration setting
> above is no longer having any effect.
>
> anyone know what might have changed in b121 that would cause this change
> in behavior?
>
> thanks
> ed
> _______________________________________________
> desktop-discuss mailing list
> desktop-discuss at opensolaris.org
