<?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: Iceweasel 3.5 on Debian Lenny</title>
	<atom:link href="http://www.oojahtech.com/2009/07/13/iceweasel-3-5-on-debian-lenny/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.oojahtech.com/2009/07/13/iceweasel-3-5-on-debian-lenny/</link>
	<description></description>
	<lastBuildDate>Fri, 16 Apr 2010 20:37:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: fishbowl</title>
		<link>http://www.oojahtech.com/2009/07/13/iceweasel-3-5-on-debian-lenny/comment-page-1/#comment-25</link>
		<dc:creator>fishbowl</dc:creator>
		<pubDate>Tue, 14 Jul 2009 11:16:56 +0000</pubDate>
		<guid isPermaLink="false">#comment-25</guid>
		<description>There might be a way to do that, I don&#039;t know entirely. I would have to do some pocking around other Debian Sites to maybe find out, which would be convenient. As for now, if a new point release of Iceweasel is available I would uncomment them and only upgrade Iceweasel; meaning I would have to keep my eye on the experimental and testing branches. Same thing If I where to use the binaries of Firefox, I would occasional have to manually update; however, in windows Firefox i have seen a built in update utility which I haven&#039;t ever encountered in Linux, but might be available with the official binaries (i don&#039;t know).</description>
		<content:encoded><![CDATA[<p>There might be a way to do that, I don&#8217;t know entirely. I would have to do some pocking around other Debian Sites to maybe find out, which would be convenient. As for now, if a new point release of Iceweasel is available I would uncomment them and only upgrade Iceweasel; meaning I would have to keep my eye on the experimental and testing branches. Same thing If I where to use the binaries of Firefox, I would occasional have to manually update; however, in windows Firefox i have seen a built in update utility which I haven&#8217;t ever encountered in Linux, but might be available with the official binaries (i don&#8217;t know).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fishbowl</title>
		<link>http://www.oojahtech.com/2009/07/13/iceweasel-3-5-on-debian-lenny/comment-page-1/#comment-24</link>
		<dc:creator>fishbowl</dc:creator>
		<pubDate>Tue, 14 Jul 2009 11:12:03 +0000</pubDate>
		<guid isPermaLink="false">#comment-24</guid>
		<description>The reason I went 64bit is mainly because my system has 4gigs of ram - but ifyou have under 3.2gigs then by all means stick with 32bit (I have encountered some frustrations with 64bit). I am considering trying the processes with the bigmem kernel to see if I can get the full 4gigs in a 32bit system.  If i where using a 32 bit system I would use the binary directly from Mozilla (it is easier to make a package for it to). I am not a compiling package making pro, and only have the vaguest idea what I am doing. With another needed package I tried compiling from source and packaging all the language libraries where included even though I already had them and with Firefox there seemed to be a lot of source code and extra files not included in the binary avalible from Firefox. I need to learn more about compiling and making packages, I think.</description>
		<content:encoded><![CDATA[<p>The reason I went 64bit is mainly because my system has 4gigs of ram &#8211; but ifyou have under 3.2gigs then by all means stick with 32bit (I have encountered some frustrations with 64bit). I am considering trying the processes with the bigmem kernel to see if I can get the full 4gigs in a 32bit system.  If i where using a 32 bit system I would use the binary directly from Mozilla (it is easier to make a package for it to). I am not a compiling package making pro, and only have the vaguest idea what I am doing. With another needed package I tried compiling from source and packaging all the language libraries where included even though I already had them and with Firefox there seemed to be a lot of source code and extra files not included in the binary avalible from Firefox. I need to learn more about compiling and making packages, I think.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Master One</title>
		<link>http://www.oojahtech.com/2009/07/13/iceweasel-3-5-on-debian-lenny/comment-page-1/#comment-23</link>
		<dc:creator>Master One</dc:creator>
		<pubDate>Tue, 14 Jul 2009 01:00:33 +0000</pubDate>
		<guid isPermaLink="false">#comment-23</guid>
		<description>I just came to the conclusion, to leave all my Desktop/Laptop installations at 32bit, because none of these machines have more than 2GB RAM, and even if the CPU in some of my computers support EM64T, it does not make any sense, especially because I want to use SMplayer with CoreAVC, which unfortunately can not be compiled on 64bit (there is a thread on Ubuntu forums concerning that proceeding). That means, there are three options:- use the binary directly available from mozilla- build it myself following the mentioned instructions- use the version from experimentalThat&#039;s hard to choose, because I was in the opinion, that compiling myself will lead to the best result. What exactly led to your own package being &quot;bloated&quot;?</description>
		<content:encoded><![CDATA[<p>I just came to the conclusion, to leave all my Desktop/Laptop installations at 32bit, because none of these machines have more than 2GB RAM, and even if the CPU in some of my computers support EM64T, it does not make any sense, especially because I want to use SMplayer with CoreAVC, which unfortunately can not be compiled on 64bit (there is a thread on Ubuntu forums concerning that proceeding). That means, there are three options:- use the binary directly available from mozilla- build it myself following the mentioned instructions- use the version from experimentalThat&#8217;s hard to choose, because I was in the opinion, that compiling myself will lead to the best result. What exactly led to your own package being &#8220;bloated&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Master One</title>
		<link>http://www.oojahtech.com/2009/07/13/iceweasel-3-5-on-debian-lenny/comment-page-1/#comment-22</link>
		<dc:creator>Master One</dc:creator>
		<pubDate>Tue, 14 Jul 2009 00:48:02 +0000</pubDate>
		<guid isPermaLink="false">#comment-22</guid>
		<description>Yes, that indeed may be the most convenient way. But how about (security) updates for Firefox/Iceweasel 3.5?If you disable the testing/experimental entries in sources.list no updates will be done. I am not a Debian expert yet, but I guess there should be a way to enable certain packages only from other releases by configuring something in /etc/apt/apt.conf.d/ ?</description>
		<content:encoded><![CDATA[<p>Yes, that indeed may be the most convenient way. But how about (security) updates for Firefox/Iceweasel 3.5?If you disable the testing/experimental entries in sources.list no updates will be done. I am not a Debian expert yet, but I guess there should be a way to enable certain packages only from other releases by configuring something in /etc/apt/apt.conf.d/ ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
