<?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 for The DF Lab</title>
	<atom:link href="http://blog.danfego.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.danfego.net</link>
	<description>A guy like me?</description>
	<lastBuildDate>Tue, 08 Jun 2010 14:32:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Upgrading Ubuntu from Jaunty to Karmic Behind a Proxy by asen</title>
		<link>http://blog.danfego.net/2009/11/upgrading-ubuntu-from-jaunty-to-karmic-behind-a-proxy/comment-page-1/#comment-7331</link>
		<dc:creator>asen</dc:creator>
		<pubDate>Tue, 08 Jun 2010 14:32:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danfego.net/?p=285#comment-7331</guid>
		<description>@Richard Baldry
Dude!  Thanks a lot.  Works like a charm.  Had I known this fix, would have been able to save atleast a couple of hours trying to search for a solution.  Anyway, better late than never :-).</description>
		<content:encoded><![CDATA[<p>@Richard Baldry<br />
Dude!  Thanks a lot.  Works like a charm.  Had I known this fix, would have been able to save atleast a couple of hours trying to search for a solution.  Anyway, better late than never <img src='http://blog.danfego.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> .</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Update to mod_rootme by Dan</title>
		<link>http://blog.danfego.net/2009/10/update-to-mod_rootme/comment-page-1/#comment-7178</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Tue, 25 May 2010 10:35:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danfego.net/?p=281#comment-7178</guid>
		<description>Yeah, I&#039;ll do that. It&#039;s a very nifty tool! Actually the version I managed to post here my friend recently pointed out was nit the version I meant to post... it&#039;s a bit off but I&#039;ll fix that soon too. Laziness is a bitch!</description>
		<content:encoded><![CDATA[<p>Yeah, I&#8217;ll do that. It&#8217;s a very nifty tool! Actually the version I managed to post here my friend recently pointed out was nit the version I meant to post&#8230; it&#8217;s a bit off but I&#8217;ll fix that soon too. Laziness is a bitch!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Update to mod_rootme by Christophe Devine</title>
		<link>http://blog.danfego.net/2009/10/update-to-mod_rootme/comment-page-1/#comment-7176</link>
		<dc:creator>Christophe Devine</dc:creator>
		<pubDate>Tue, 25 May 2010 08:55:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danfego.net/?p=281#comment-7176</guid>
		<description>That&#039;s awesome, I had no idea five years ago this project would live on, congrats ^^ Btw, do you mind submitting your version to packetstormsecurity ? This way it will be included with the previous versions.</description>
		<content:encoded><![CDATA[<p>That&#8217;s awesome, I had no idea five years ago this project would live on, congrats ^^ Btw, do you mind submitting your version to packetstormsecurity ? This way it will be included with the previous versions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Upgrading Ubuntu from Jaunty to Karmic Behind a Proxy by Tim B</title>
		<link>http://blog.danfego.net/2009/11/upgrading-ubuntu-from-jaunty-to-karmic-behind-a-proxy/comment-page-1/#comment-7108</link>
		<dc:creator>Tim B</dc:creator>
		<pubDate>Thu, 20 May 2010 00:46:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danfego.net/?p=285#comment-7108</guid>
		<description>Richard&#039;s hack works wonders - upgrading to 10.04 on my laptop at work now, although I did have to slightly modify the hack. Had to match the indent of the lines below and leave off the semi-colon.

Also, remember to add the proxy username and password to apt.conf if you need one! I forgot the first time, and was left wondering why it was still failing (though not hanging at least).</description>
		<content:encoded><![CDATA[<p>Richard&#8217;s hack works wonders &#8211; upgrading to 10.04 on my laptop at work now, although I did have to slightly modify the hack. Had to match the indent of the lines below and leave off the semi-colon.</p>
<p>Also, remember to add the proxy username and password to apt.conf if you need one! I forgot the first time, and was left wondering why it was still failing (though not hanging at least).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gnome Do Theme Issue by Berk</title>
		<link>http://blog.danfego.net/2009/06/gnome-do-theme-issue/comment-page-1/#comment-6988</link>
		<dc:creator>Berk</dc:creator>
		<pubDate>Sat, 08 May 2010 22:55:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danfego.net/?p=256#comment-6988</guid>
		<description>Update: The problem still happens but less frequently. If you have any idea what causes this please let me know. Berk</description>
		<content:encoded><![CDATA[<p>Update: The problem still happens but less frequently. If you have any idea what causes this please let me know. Berk</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Gnome Do Theme Issue by Berk</title>
		<link>http://blog.danfego.net/2009/06/gnome-do-theme-issue/comment-page-1/#comment-6896</link>
		<dc:creator>Berk</dc:creator>
		<pubDate>Fri, 07 May 2010 20:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danfego.net/?p=256#comment-6896</guid>
		<description>I had an intermittent problem where gnome-do would not work on start-ups. I&#039;d write firefox for example and only see the letters I wrote and not the Firefox logo. This solved the problem. Thanks!</description>
		<content:encoded><![CDATA[<p>I had an intermittent problem where gnome-do would not work on start-ups. I&#8217;d write firefox for example and only see the letters I wrote and not the Firefox logo. This solved the problem. Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Upgrading Ubuntu from Jaunty to Karmic Behind a Proxy by Dan</title>
		<link>http://blog.danfego.net/2009/11/upgrading-ubuntu-from-jaunty-to-karmic-behind-a-proxy/comment-page-1/#comment-6857</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Mon, 03 May 2010 12:45:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danfego.net/?p=285#comment-6857</guid>
		<description>&lt;a href=&quot;#comment-6833&quot; rel=&quot;nofollow&quot;&gt;@Richard Baldry&lt;/a&gt;
Ah Richard, you&#039;re the problem-solver I can&#039;t muster in myself in the morning. :-) Thanks for the hack!</description>
		<content:encoded><![CDATA[<p><a href="#comment-6833" rel="nofollow">@Richard Baldry</a><br />
Ah Richard, you&#8217;re the problem-solver I can&#8217;t muster in myself in the morning. <img src='http://blog.danfego.net/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  Thanks for the hack!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Upgrading Ubuntu from Jaunty to Karmic Behind a Proxy by buge</title>
		<link>http://blog.danfego.net/2009/11/upgrading-ubuntu-from-jaunty-to-karmic-behind-a-proxy/comment-page-1/#comment-6854</link>
		<dc:creator>buge</dc:creator>
		<pubDate>Mon, 03 May 2010 07:51:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danfego.net/?p=285#comment-6854</guid>
		<description>&lt;a href=&quot;#comment-6833&quot; rel=&quot;nofollow&quot;&gt;@Richard Baldry&lt;/a&gt; Thanks for the hack! I managed to successfully upgrade that way. It&#039;s annoying that there seems to be a proxy bug of some sort in every release.</description>
		<content:encoded><![CDATA[<p><a href="#comment-6833" rel="nofollow">@Richard Baldry</a> Thanks for the hack! I managed to successfully upgrade that way. It&#8217;s annoying that there seems to be a proxy bug of some sort in every release.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Upgrading Ubuntu from Jaunty to Karmic Behind a Proxy by Richard Baldry</title>
		<link>http://blog.danfego.net/2009/11/upgrading-ubuntu-from-jaunty-to-karmic-behind-a-proxy/comment-page-1/#comment-6833</link>
		<dc:creator>Richard Baldry</dc:creator>
		<pubDate>Fri, 30 Apr 2010 18:43:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danfego.net/?p=285#comment-6833</guid>
		<description>I&#039;ve just tried upgrading to Lucid from Jaunty behind a proxy and experienced the same problem.

The problem is not authenticating vs non-authenticating proxy. It happens with any explicit proxy - any situation where you have to specify a proxy address in order for any HTTP to work.

The problem stems from the function url_downloadable() in /usr/lib/python2.6/dist-packages/UpdateManager/Core/utils.py. It looks like this function is called during the process of deciding which mirror to use. The intent of this function is simply to check whether a given URL works and I think it is used here to check whether a given mirror is up and available and serving the right files.

Unfortunately something in the way this function invokes the http library  means that the proxy settings are ignored. The library tries to make a direct connection to the site serving the url in question. You can see this by running &#039;netstat -at&#039; while the update process is hung - you will see a connection to a canonical.com host in the SYN_SENT state.

I don&#039;t have the inclination at this stage to work out how to re-plumb all this so the url_downloadable() check does respect proxy settings. However, I did use the following hack to make the installation work:

$ sudo vi /usr/lib/python2.6/dist-packages/UpdateManager/Core/utils.py

Search for the &#039;url_downloadable&#039; function def. Now look for the following lines of code within that function and add &#039;return True;&#039; as shown:
    if scheme == &quot;http&quot;:
    import httplib
    try:
      return True;
      c = httplib.HTTPConnection(netloc)
      c.request(&quot;HEAD&quot;, path)

This basically bypasses the &#039;url_downloadable&#039; check and forces the upgrade process to assume it&#039;s succeeded. When the upgrade process comes to actually download and install stuff, it uses the proxy settings correctly.

This is clearly a bug in the Upgrade process.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just tried upgrading to Lucid from Jaunty behind a proxy and experienced the same problem.</p>
<p>The problem is not authenticating vs non-authenticating proxy. It happens with any explicit proxy &#8211; any situation where you have to specify a proxy address in order for any HTTP to work.</p>
<p>The problem stems from the function url_downloadable() in /usr/lib/python2.6/dist-packages/UpdateManager/Core/utils.py. It looks like this function is called during the process of deciding which mirror to use. The intent of this function is simply to check whether a given URL works and I think it is used here to check whether a given mirror is up and available and serving the right files.</p>
<p>Unfortunately something in the way this function invokes the http library  means that the proxy settings are ignored. The library tries to make a direct connection to the site serving the url in question. You can see this by running &#8216;netstat -at&#8217; while the update process is hung &#8211; you will see a connection to a canonical.com host in the SYN_SENT state.</p>
<p>I don&#8217;t have the inclination at this stage to work out how to re-plumb all this so the url_downloadable() check does respect proxy settings. However, I did use the following hack to make the installation work:</p>
<p>$ sudo vi /usr/lib/python2.6/dist-packages/UpdateManager/Core/utils.py</p>
<p>Search for the &#8216;url_downloadable&#8217; function def. Now look for the following lines of code within that function and add &#8216;return True;&#8217; as shown:<br />
    if scheme == &#8220;http&#8221;:<br />
    import httplib<br />
    try:<br />
      return True;<br />
      c = httplib.HTTPConnection(netloc)<br />
      c.request(&#8220;HEAD&#8221;, path)</p>
<p>This basically bypasses the &#8216;url_downloadable&#8217; check and forces the upgrade process to assume it&#8217;s succeeded. When the upgrade process comes to actually download and install stuff, it uses the proxy settings correctly.</p>
<p>This is clearly a bug in the Upgrade process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fixing NVIDIA driver issues on Ubuntu Karmic by george</title>
		<link>http://blog.danfego.net/2009/11/fixing-nvidia-driver-issues-on-ubuntu-karmic/comment-page-1/#comment-5358</link>
		<dc:creator>george</dc:creator>
		<pubDate>Fri, 29 Jan 2010 10:55:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.danfego.net/?p=290#comment-5358</guid>
		<description>i get the same as ramon install archives failed. this was all working fine on my karmic then my gl drivers stopped working so i tried to reinstall the 185 driver and then i have run into problems. i have done this many times in the past without problems (first removing the driver with sudo sh NVIDIA* --uninstall) and then reinstalling with sudo sh NVIDIA* so im wonderinf now why this doesnt work.

having them looked at the dkms problem (dkms status), and then using this jockey idea (which shows clearly that although i have removed nvidia i havent removed everything because it shows that i have 185, 190, and 195 (all of which i have tried and supposedly removed) still there but disabled and not in use.

it seems that if there was a way to completely remove all these drivers to avoid conflicts and start again it would proably solve the probelms, although i havent yet sem how to do this.</description>
		<content:encoded><![CDATA[<p>i get the same as ramon install archives failed. this was all working fine on my karmic then my gl drivers stopped working so i tried to reinstall the 185 driver and then i have run into problems. i have done this many times in the past without problems (first removing the driver with sudo sh NVIDIA* &#8211;uninstall) and then reinstalling with sudo sh NVIDIA* so im wonderinf now why this doesnt work.</p>
<p>having them looked at the dkms problem (dkms status), and then using this jockey idea (which shows clearly that although i have removed nvidia i havent removed everything because it shows that i have 185, 190, and 195 (all of which i have tried and supposedly removed) still there but disabled and not in use.</p>
<p>it seems that if there was a way to completely remove all these drivers to avoid conflicts and start again it would proably solve the probelms, although i havent yet sem how to do this.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

