https://bugzilla.novell.com/show_bug.cgi?id=413083
User ms@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=413083#c16
Marcus Schaefer changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|ms@novell.com |sndirsch@novell.com
--- Comment #16 from Marcus Schaefer 2008-09-09 04:54:53 MDT ---
Let me first tell you Scott that in the past we had a check at boot
time if the hardware has changed (hardware ID's) If that happened sax2
was called in re-init mode and provided a clean new proposal for the
_complete_ X11 subsystem. So if the user plugged in a new monitor he
got a new proposal, if he plugs in a new mouse using its own mouse driver
the same happened. The short answer to all this was "people hated it"
* they don't want some magic at boot time
* they don't want to setup their custom resolution just because the
mouse has changed
To some degree I can understand that but it would also be a bad idea to
handle the different parts of the X11 subsystem as unique entities because
they aren't unique. Many of them conflict with each other and you can't
compare the old situation with the new one without creating other problems
and that even applies to the mouse. The best example is a synaptics touchpad
which can't be the core mouse so if you had a standard mouse before the
system will break by that change without a new configuration. You can
claim that are bugs in X and most probably you are right but I spent a
couple of years to find out that nobody cares of that kind of problems
people stumble over.
We decided to offer a complete setup which we can control and which we can
offer as _working_. But we disabled the reprobe code at boot time because we
had to
A possible solution seems to happen in X itself. The possibility of the
X-Server to probe and Identify changes at startup and the removal of the
static configuration file xorg.conf will allow people to change everything
and they can use GUI applications to change other data on the fly
I think this is the way to go for the future.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.