[PATCH 0/3] xfree86: Configure input devices by properties

Alan Coopersmith Alan.Coopersmith at Sun.COM
Mon Oct 5 11:14:36 PDT 2009

Dan Nicholson wrote:
> True. The single file xorg.conf is not a lot of fun. To that end, I'm
> also working on a patch to make an xorg configuration directory.
> Something like /etc/X11/xorg.conf.d/. 

I've thought of this before, especially since our old Xsun server had a
similar concept of OS-provided default configuration, with a system-specific
configuration file that just supplied the non-default settings - a bunch of
stuff we have embedded in the C code is really default xorg.conf that could
be in system provided conf files.

> The huge advantage of using
> xorg.conf is that you and your users can be entirely ignorant of how
> the event backend. Nobody enjoyed migrating their configurations to
> hal (in fact many people are still fighting it), and hal is already
> deprecated! At least on linux, the push is to get people off hal and
> onto udev. Or maybe a new DeviceKit will show up. Or maybe on Solaris
> they want to use a different mechanism. 

I really don't want to use udev - we already have most of the same functionality
in Solaris native interfaces, except for the attachment of random metadata to
the devices.   Trying to graft the Solaris native API's into what's really a
Linux native API is going to be painful for all sides, and a lot of work neither
of us should have to do.   But I also don't want to have input device
configuration be completely platform-specific, which is why I like the xorg.conf

	-Alan Coopersmith-           alan.coopersmith at sun.com
	 Sun Microsystems, Inc. - X Window System Engineering

More information about the xorg-devel mailing list