[PATCH kdrive/ephyr v7 5/9] kdrive: add options to set default XKB properties

Peter Hutterer peter.hutterer at who-t.net
Tue Feb 9 04:23:59 UTC 2016

On Mon, Feb 08, 2016 at 10:00:21PM -0200, LaƩrcio de Sousa wrote:
> Em 8 de fev de 2016 17:54, "Adam Jackson" <ajax at nwnk.net> escreveu:
> > How are you in a scenario where you can pass these values to Xephyr on
> > the command line, but can't modify the udev properties?
> Well... What I really mean is a scenario where neither the Linux distro,
> nor the keyboard vendor, nor the sysadmin him(her)self provides any udev
> rules to set XKB properties.
> For example, I know there are some distros that ship a set of default udev
> rules to set XKB properties, but not all of them do it (at least the one I
> used when I wrote this patch didn't).

when we introduced the udev config backend we mostly agreed that we weren't
going to use udev as a config storage (which is how InputClass was
conceived). Debian ships them because there was some release timing conflict
where the udev patches where ready but the InputClass bits weren't but aside
from Debian I don't expect any distro to set the xkb config via udev.

aside from bikeshedding that I prefer -xkb-layout over -xkblayout this makes


More information about the xorg-devel mailing list