On Wed, Dec 16, 2009 at 5:27 PM, Dan Nicholson wrote:
> >
> > Hi Dan,
> >
> > While sorting through my customers' requests for wacom X driver related
> > issues, I encountered another "unusual" situation:
> >
> > How can we explicitly let X server ignore a device on a hotplugging
> enabled
> > s
On Wed, Dec 16, 2009 at 5:14 PM, Ping wrote:
> On Mon, Dec 14, 2009 at 2:59 PM, Ping wrote:
>>
>> On Mon, Dec 14, 2009 at 7:36 AM, Dan Nicholson
>> wrote:
>>>
>>> I think it will work the way you envision, but with the caveat that
>>> there isn't any parsing of ~/.xorg.conf and never has been. A
On Mon, Dec 14, 2009 at 2:59 PM, Ping wrote:
> On Mon, Dec 14, 2009 at 7:36 AM, Dan Nicholson wrote:
>
>> I think it will work the way you envision, but with the caveat that
>> there isn't any parsing of ~/.xorg.conf and never has been. After
>> that, it would work similarly to how you describe.
On Mon, Dec 14, 2009 at 7:36 AM, Dan Nicholson wrote:
> I think it will work the way you envision, but with the caveat that
> there isn't any parsing of ~/.xorg.conf and never has been. After
> that, it would work similarly to how you describe. xorg.conf is parsed
> first and then the xorg.conf.d
Dan Nicholson wrote:
> I think it will work the way you envision, but with the caveat that
> there isn't any parsing of ~/.xorg.conf and never has been.
There actually was in the past, but only for the root user, and that
was dropped a while ago (maybe 1.5 or 1.6? git will tell you).
--
On Sun, Dec 13, 2009 at 12:05 PM, Ping wrote:
> I've hesitated on replying to this email string for a while. With my
> limited view of X server (x.org as well), I fear I am not seeing the whole
> picture. However, for the sake of Wacom device driver, the worst response I
> might get would be some
I've hesitated on replying to this email string for a while. With my
limited view of X server (x.org as well), I fear I am not seeing the whole
picture. However, for the sake of Wacom device driver, the worst response I
might get would be someone tells me that I don't know what I am talking
about.
On Mon, Dec 07, 2009 at 09:07:01PM -0800, Dan Nicholson wrote:
> > How about:
> > * -config can be specified multiple times
> > * directories can be specified as well as files
> > * any specification on the command line overrides the default
> > * the default is $(sysconfdir)/X11/xorg.conf:$(sy
On Mon, Dec 7, 2009 at 8:05 PM, Daniel Stone wrote:
> On Tue, Dec 08, 2009 at 12:47:26PM +1000, Peter Hutterer wrote:
>> On Mon, Dec 07, 2009 at 06:33:41PM -0800, Alan Coopersmith wrote:
>> > Peter Hutterer wrote:
>> > > One more thing about this patchset. what's the behaviour if the server is
>>
On Mon, Dec 7, 2009 at 6:47 PM, Peter Hutterer wrote:
> On Mon, Dec 07, 2009 at 06:33:41PM -0800, Alan Coopersmith wrote:
>> Peter Hutterer wrote:
>> > One more thing about this patchset. what's the behaviour if the server is
>> > run with Xorg -config foobar.conf?
>> >
>> > Does it still scan xor
On Tue, Dec 08, 2009 at 12:47:26PM +1000, Peter Hutterer wrote:
> On Mon, Dec 07, 2009 at 06:33:41PM -0800, Alan Coopersmith wrote:
> > Peter Hutterer wrote:
> > > One more thing about this patchset. what's the behaviour if the server is
> > > run with Xorg -config foobar.conf?
> > >
> > > Does it
On Mon, Dec 07, 2009 at 06:33:41PM -0800, Alan Coopersmith wrote:
> Peter Hutterer wrote:
> > One more thing about this patchset. what's the behaviour if the server is
> > run with Xorg -config foobar.conf?
> >
> > Does it still scan xorg.conf.d? If so, we need an option to disable that so
> > one
Peter Hutterer wrote:
> One more thing about this patchset. what's the behaviour if the server is
> run with Xorg -config foobar.conf?
>
> Does it still scan xorg.conf.d? If so, we need an option to disable that so
> one can force _only_ the use of a custom xorg.conf, without system
> configuratio
On Fri, Nov 27, 2009 at 09:34:00AM -0800, Dan Nicholson wrote:
> Currently there is a single file, xorg.conf, for configuring the server.
> This works fine most of the time, but it becomes a problem when packages
> or system services need to adjust the configuration. Instead, allow
> multiple confi
On Tue, Dec 01, 2009 at 06:10:58AM -0800, Dan Nicholson wrote:
> >> /*
> >> * prototypes for public functions
> >> */
> >> -extern _X_EXPORT const char *xf86openConfigFile (const char *, const char
> >> *,
> >> - const char *);
> >> +extern _X_EXPORT const
On Mon, Nov 30, 2009 at 6:14 PM, Peter Hutterer
wrote:
> On Fri, Nov 27, 2009 at 09:34:00AM -0800, Dan Nicholson wrote:
>> Currently there is a single file, xorg.conf, for configuring the server.
>> This works fine most of the time, but it becomes a problem when packages
>> or system services need
On Tue, Dec 1, 2009 at 1:02 AM, Julien Cristau wrote:
> On Tue, Dec 1, 2009 at 12:14:46 +1000, Peter Hutterer wrote:
>
>> the HAL code may be a good source for this since it does exactly the same.
>> http://cgit.freedesktop.org/hal/tree/hald/create_cache.c
>> (copying that would also add recursiv
On Tue, Dec 1, 2009 at 12:14:46 +1000, Peter Hutterer wrote:
> the HAL code may be a good source for this since it does exactly the same.
> http://cgit.freedesktop.org/hal/tree/hald/create_cache.c
> (copying that would also add recursive subdirectory support :)
>
The hal code seems to be GPL2+,
On Fri, Nov 27, 2009 at 09:34:00AM -0800, Dan Nicholson wrote:
> Currently there is a single file, xorg.conf, for configuring the server.
> This works fine most of the time, but it becomes a problem when packages
> or system services need to adjust the configuration. Instead, allow
> multiple confi
Currently there is a single file, xorg.conf, for configuring the server.
This works fine most of the time, but it becomes a problem when packages
or system services need to adjust the configuration. Instead, allow
multiple configuration files to live in a directory. Typically this will
be /etc/X11/
20 matches
Mail list logo
