<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: dpkg-reconfigure xserver-xorg</title>
	<atom:link href="http://blogs.gnome.org/bolsh/2008/07/04/dpkg-reconfigure-xserver-xorg/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/bolsh/2008/07/04/dpkg-reconfigure-xserver-xorg/</link>
	<description>Dave Neary's view of the world</description>
	<lastBuildDate>Sun, 11 Dec 2011 14:17:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: David Nusinow</title>
		<link>http://blogs.gnome.org/bolsh/2008/07/04/dpkg-reconfigure-xserver-xorg/comment-page-1/#comment-1636</link>
		<dc:creator>David Nusinow</dc:creator>
		<pubDate>Fri, 04 Jul 2008 15:38:02 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2008/07/04/dpkg-reconfigure-xserver-xorg/#comment-1636</guid>
		<description>Vladimir, yes 915-resolution is totally obsolete as of the switch from i810 to intel (1.x-&gt;2.x). You shouldn&#039;t use it any more.</description>
		<content:encoded><![CDATA[<p>Vladimir, yes 915-resolution is totally obsolete as of the switch from i810 to intel (1.x-&gt;2.x). You shouldn&#8217;t use it any more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aurélien Gâteau</title>
		<link>http://blogs.gnome.org/bolsh/2008/07/04/dpkg-reconfigure-xserver-xorg/comment-page-1/#comment-1635</link>
		<dc:creator>Aurélien Gâteau</dc:creator>
		<pubDate>Fri, 04 Jul 2008 13:03:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2008/07/04/dpkg-reconfigure-xserver-xorg/#comment-1635</guid>
		<description>I can feel your pain. While upgrading seems to work most of the time, it&#039;s usually not as clean as reinstalling.
After years of dist-upgrading my Ubuntu box (from Hoary to Hardy...), I decided it&#039;s safer to just reinstall from scratch.</description>
		<content:encoded><![CDATA[<p>I can feel your pain. While upgrading seems to work most of the time, it&#8217;s usually not as clean as reinstalling.<br />
After years of dist-upgrading my Ubuntu box (from Hoary to Hardy&#8230;), I decided it&#8217;s safer to just reinstall from scratch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Nusinow</title>
		<link>http://blogs.gnome.org/bolsh/2008/07/04/dpkg-reconfigure-xserver-xorg/comment-page-1/#comment-1634</link>
		<dc:creator>David Nusinow</dc:creator>
		<pubDate>Fri, 04 Jul 2008 12:19:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2008/07/04/dpkg-reconfigure-xserver-xorg/#comment-1634</guid>
		<description>The reason for that is pretty simple. Many many people have custom options that remain necessary in the current X server, and we didn&#039;t want to break those configurations. If people are able to manage their own xorg.conf, I assumed that they know what they were doing and didn&#039;t mess with their systems. 

The ultimate goal, still in progress, is to get rid of xorg.conf all together except in extreme cases, at which point this problem goes away. We&#039;re pretty close now, since we don&#039;t need to specify very much which means that the package scripts can ignore all those old sections entirely (fonts, modules, etc), but there&#039;s still a ways to go. If some of the more hardcore stuff like input config moves in to HAL config files then we won&#039;t have to worry about xorg.conf, and whatever the user puts in should remain relevant.</description>
		<content:encoded><![CDATA[<p>The reason for that is pretty simple. Many many people have custom options that remain necessary in the current X server, and we didn&#8217;t want to break those configurations. If people are able to manage their own xorg.conf, I assumed that they know what they were doing and didn&#8217;t mess with their systems. </p>
<p>The ultimate goal, still in progress, is to get rid of xorg.conf all together except in extreme cases, at which point this problem goes away. We&#8217;re pretty close now, since we don&#8217;t need to specify very much which means that the package scripts can ignore all those old sections entirely (fonts, modules, etc), but there&#8217;s still a ways to go. If some of the more hardcore stuff like input config moves in to HAL config files then we won&#8217;t have to worry about xorg.conf, and whatever the user puts in should remain relevant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vladimir Prus</title>
		<link>http://blogs.gnome.org/bolsh/2008/07/04/dpkg-reconfigure-xserver-xorg/comment-page-1/#comment-1633</link>
		<dc:creator>Vladimir Prus</dc:creator>
		<pubDate>Fri, 04 Jul 2008 10:48:41 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/bolsh/2008/07/04/dpkg-reconfigure-xserver-xorg/#comment-1633</guid>
		<description>Do you mean that 915resolution is no longer necessary?

Anyway, reconfigure had no effect on X-hangs-on-every-second resume behaviour I get with Hardy :-/</description>
		<content:encoded><![CDATA[<p>Do you mean that 915resolution is no longer necessary?</p>
<p>Anyway, reconfigure had no effect on X-hangs-on-every-second resume behaviour I get with Hardy <img src='http://blogs.gnome.org/bolsh/wp-content/mu-plugins/tango-smilies/tango/face-uncertain.png' alt=':-/' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blogs.gnome.org/bolsh/2008/07/04/dpkg-reconfigure-xserver-xorg/feed/ ) in 0.28365 seconds, on Feb 11th, 2012 at 2:42 am UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 11th, 2012 at 3:42 am UTC -->
