On Tue, Feb 9, 2016 at 14:23:59 +1000, Peter Hutterer wrote: > 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" <a...@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. > At this point it's not so much a timing conflict as the fact that we use /etc/default/keyboard to configure the layout for console and X, and getting information from there into the udev db seems easier/saner than generating an xorg.conf snippet in /run whenever the actual config source changes (or whenever X starts, or on boot, or...). Unless I'm missing some other way to get that info in the right place?
Cheers, Julien _______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
