<?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: The road through Ubuntu</title>
	<atom:link href="http://blog.bigsmoke.us/2008/11/27/the-way-of-ubuntu/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.bigsmoke.us/2008/11/27/the-way-of-ubuntu</link>
	<description>Smokes your problems, coughs fresh air.</description>
	<lastBuildDate>Sat, 04 Feb 2012 20:03:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: halfgaar</title>
		<link>http://blog.bigsmoke.us/2008/11/27/the-way-of-ubuntu#comment-71773</link>
		<dc:creator>halfgaar</dc:creator>
		<pubDate>Mon, 01 Dec 2008 16:13:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bigsmoke.us/?p=170#comment-71773</guid>
		<description>Actually, Xerox solved the problem by reformatting and reinstalling the Linux operating system that these things use. I&#039;d call that going after a fly with a bazooka, because all that would have been necessary is just removing the queue files and possibly restarting the print spooler.

And, about the print jobs that get stuck in Linux, that&#039;s not due to a shitty printer, but due to shitty printer driver/architecture. For some printers, CUPS uses foomatic perl scripts to handle the jobs. This is what causes those problems. When the job has been passed to the script, there is no way of stopping it, except killing it; as root, because the script runs as root.</description>
		<content:encoded><![CDATA[<p>Actually, Xerox solved the problem by reformatting and reinstalling the Linux operating system that these things use. I&#8217;d call that going after a fly with a bazooka, because all that would have been necessary is just removing the queue files and possibly restarting the print spooler.</p>
<p>And, about the print jobs that get stuck in Linux, that&#8217;s not due to a shitty printer, but due to shitty printer driver/architecture. For some printers, CUPS uses foomatic perl scripts to handle the jobs. This is what causes those problems. When the job has been passed to the script, there is no way of stopping it, except killing it; as root, because the script runs as root.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BigSmoke &#187; Getting my sister to forget the Google Desktop newsticker</title>
		<link>http://blog.bigsmoke.us/2008/11/27/the-way-of-ubuntu#comment-71621</link>
		<dc:creator>BigSmoke &#187; Getting my sister to forget the Google Desktop newsticker</dc:creator>
		<pubDate>Thu, 27 Nov 2008 20:56:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bigsmoke.us/?p=170#comment-71621</guid>
		<description>[...] she kept it permanently visible at the right side of her screen. (What a news junkie!) Now that I got her stuck with Linux, she misses her precious Google Desktop and I&#8217;m trying to figure out an alternative for [...]</description>
		<content:encoded><![CDATA[<p>[...] she kept it permanently visible at the right side of her screen. (What a news junkie!) Now that I got her stuck with Linux, she misses her precious Google Desktop and I&#8217;m trying to figure out an alternative for [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

