1 |
On Thu, 2010-12-30 at 19:02 +0000, Mick wrote: |
2 |
> On Thursday 30 December 2010 17:40:18 Mike Edenfield wrote: |
3 |
> > On Wed, 2010-12-29 at 13:01 +0000, Mick wrote: |
4 |
> > > Personally, I can't see why all these additional config files and |
5 |
> > > locations are required, rather than a single /etc/X11/xorg.conf. I have |
6 |
> > > found all these back and forth changes to fdi's, xorg.conf.d and what |
7 |
> > > have you, unnecessary and annoyingly time wastin |
8 |
> > > |
9 |
> > > Of course I might have missed something simple in all this kerfuffle, so |
10 |
> > > please chime in if there is a better way around this. |
11 |
> > |
12 |
> > If all you are worried about is making your touchpad work in X, and |
13 |
> > you're willing to pull it up in a text editor every time you need to |
14 |
> > make a change, then no, you didn't really miss anything. |
15 |
> |
16 |
> Well, it's the touch pad and keyboard on two laptops, both of which seem to |
17 |
> not have liked evdev defaults, or modifying xorg.conf, or adding options to |
18 |
> the evdev file itself, or adding options to the 50-synaptics.conf file, or a |
19 |
> 10-keyboard.conf file that I created. |
20 |
> |
21 |
> On the other hand, with a desktop the transition to 1.9 two months or so ago |
22 |
> just worked™. |
23 |
> |
24 |
> > The purpose of xorg.conf.d is to allow packages/utilities/etc to drop in |
25 |
> > changes to your X config seamlessly, as in, without the user being |
26 |
> > required to take any specific action. For example, the synaptics input |
27 |
> > driver drops a 50-synaptics.conf file into your xorg.conf.d that |
28 |
> > includes a simple "this is a touchpad" configuration, which would take |
29 |
> > effect just by restarting X. |
30 |
> |
31 |
> Are you talking about the /usr/share/X11/xorg.conf.d/ directory or the |
32 |
> /etc/X11/xorg.conf.d/ which I created on my own? I was hoping that any |
33 |
> additions in /etc/X11/xorg.conf.d/ would take precedence over settings in |
34 |
> /usr/share/X11/xorg.conf.d/ and survive an update, but the two seem to clash |
35 |
> and cause erratic behaviour. |
36 |
|
37 |
If you have a file of the same name in both directories, then the one |
38 |
in /etc should override the one in /usr/share. But the names need to |
39 |
match exactly. |