public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Edenfield <kutulu@kutulu.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xorg-server
Date: Thu, 30 Dec 2010 12:40:18 -0500	[thread overview]
Message-ID: <1293730818.28544.10.camel@platypus> (raw)
In-Reply-To: <201012291301.35032.michaelkintzios@gmail.com>

On Wed, 2010-12-29 at 13:01 +0000, Mick wrote:

> Personally, I can't see why all these additional config files and locations 
> are required, rather than a single /etc/X11/xorg.conf.  I have found all these 
> back and forth changes to fdi's, xorg.conf.d and what have you, unnecessary 
> and annoyingly time wasting.
> 
> Of course I might have missed something simple in all this kerfuffle, so 
> please chime in if there is a better way around this.

If all you are worried about is making your touchpad work in X, and
you're willing to pull it up in a text editor every time you need to
make a change, then no, you didn't really miss anything.

The purpose of xorg.conf.d is to allow packages/utilities/etc to drop in
changes to your X config seamlessly, as in, without the user being
required to take any specific action.  For example, the synaptics input
driver drops a 50-synaptics.conf file into your xorg.conf.d that
includes a simple "this is a touchpad" configuration, which would take
effect just by restarting X.  

The purpose of udev is to configure all of the hardware on your system,
not just for X.  It's how GNOME/KDE/whatever is able to automount your
USB key when it shows up, and knows that /dev/sr0 is a dvd-rom drive,
etc. Just as with HAL, using udev to configure X-specific options is
probably overkill. In theory, other GUI systems besides X could just as
easily read the x11 options from udev and use them. Since there isn't
really any such alternative, the practical benefits of udev over a
monolithic xorg.conf file mostly vanish.

--Mike




  parent reply	other threads:[~2010-12-30 18:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <g4jho-61J-11@gated-at.bofh.it>
2010-12-27 17:58 ` [gentoo-user] xorg-server David W Noon
2010-12-27 18:45   ` John
2010-12-27 19:20     ` Neil Bothwick
2010-12-27 20:23       ` Mick
2010-12-29  9:26   ` Konstantinos Agouros
2010-12-29 13:01     ` Mick
2010-12-29 13:42       ` Dale
2010-12-29 14:49       ` Neil Bothwick
2010-12-30 17:40       ` Mike Edenfield [this message]
2010-12-30 19:02         ` Mick
2010-12-30 19:43           ` Mike Edenfield
2010-12-30 23:01             ` Mick
2020-04-14 18:16 Jorge Almeida
2020-04-14 18:29 ` tastytea
2020-04-14 18:47   ` Jorge Almeida
2020-04-14 20:22     ` Dale
2020-04-14 20:36       ` Jorge Almeida
     [not found] <g4pGa-8uT-19@gated-at.bofh.it>
     [not found] ` <g4qiR-VE-7@gated-at.bofh.it>
     [not found]   ` <g4qVA-24v-5@gated-at.bofh.it>
     [not found]     ` <g4rRD-3EB-9@gated-at.bofh.it>
2010-12-27 21:39       ` David W Noon
2010-12-27 22:43         ` Mick
     [not found] ` <g4pGa-8uT-17@gated-at.bofh.it>
     [not found]   ` <g50FI-3yD-5@gated-at.bofh.it>
2010-12-29 14:25     ` David W Noon
  -- strict thread matches above, loose matches on Subject: below --
2010-12-27 11:14 John
2010-12-27 11:29 ` Neil Bothwick
2010-12-27 11:39 ` Dale
2006-01-13 13:08 krgn
2006-01-14  2:03 ` Richard Fish

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1293730818.28544.10.camel@platypus \
    --to=kutulu@kutulu.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox