1 |
On Thursday 30 December 2010 17:40:18 Mike Edenfield wrote: |
2 |
> On Wed, 2010-12-29 at 13:01 +0000, Mick wrote: |
3 |
> > Personally, I can't see why all these additional config files and |
4 |
> > locations are required, rather than a single /etc/X11/xorg.conf. I have |
5 |
> > found all these back and forth changes to fdi's, xorg.conf.d and what |
6 |
> > have you, unnecessary and annoyingly time wasting. |
7 |
> > |
8 |
> > Of course I might have missed something simple in all this kerfuffle, so |
9 |
> > please chime in if there is a better way around this. |
10 |
> |
11 |
> If all you are worried about is making your touchpad work in X, and |
12 |
> you're willing to pull it up in a text editor every time you need to |
13 |
> make a change, then no, you didn't really miss anything. |
14 |
|
15 |
Well, it's the touch pad and keyboard on two laptops, both of which seem to |
16 |
not have liked evdev defaults, or modifying xorg.conf, or adding options to |
17 |
the evdev file itself, or adding options to the 50-synaptics.conf file, or a |
18 |
10-keyboard.conf file that I created. |
19 |
|
20 |
On the other hand, with a desktop the transition to 1.9 two months or so ago |
21 |
just worked™. |
22 |
|
23 |
> The purpose of xorg.conf.d is to allow packages/utilities/etc to drop in |
24 |
> changes to your X config seamlessly, as in, without the user being |
25 |
> required to take any specific action. For example, the synaptics input |
26 |
> driver drops a 50-synaptics.conf file into your xorg.conf.d that |
27 |
> includes a simple "this is a touchpad" configuration, which would take |
28 |
> effect just by restarting X. |
29 |
|
30 |
Are you talking about the /usr/share/X11/xorg.conf.d/ directory or the |
31 |
/etc/X11/xorg.conf.d/ which I created on my own? I was hoping that any |
32 |
additions in /etc/X11/xorg.conf.d/ would take precedence over settings in |
33 |
/usr/share/X11/xorg.conf.d/ and survive an update, but the two seem to clash |
34 |
and cause erratic behaviour. |
35 |
|
36 |
|
37 |
> The purpose of udev is to configure all of the hardware on your system, |
38 |
> not just for X. It's how GNOME/KDE/whatever is able to automount your |
39 |
> USB key when it shows up, and knows that /dev/sr0 is a dvd-rom drive, |
40 |
> etc. Just as with HAL, using udev to configure X-specific options is |
41 |
> probably overkill. In theory, other GUI systems besides X could just as |
42 |
> easily read the x11 options from udev and use them. Since there isn't |
43 |
> really any such alternative, the practical benefits of udev over a |
44 |
> monolithic xorg.conf file mostly vanish. |
45 |
|
46 |
Yes it does make sense, but I sort of objected to tweaking udev rules because |
47 |
I'm thinking the clash is not between devices, but between xf86 drivers. |
48 |
|
49 |
Anyhow, I'm happy I got it working regardless. :-) |
50 |
-- |
51 |
Regards, |
52 |
Mick |