<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Linux Tips &#8211; Pack I</title>
	<atom:link href="http://www.g-loaded.eu/2006/04/08/linux-tips-pack-i/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.g-loaded.eu/2006/04/08/linux-tips-pack-i/</link>
	<description>An open-source software and technology related journal</description>
	<lastBuildDate>Fri, 03 Feb 2012 18:35:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Gnot</title>
		<link>http://www.g-loaded.eu/2006/04/08/linux-tips-pack-i/#comment-717</link>
		<dc:creator>Gnot</dc:creator>
		<pubDate>Fri, 28 Apr 2006 18:05:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/2006/04/08/linux-tips-pack-i/#comment-717</guid>
		<description>I guess I was too lazy to create separate posts for each one of them, but certainly it would be better to have them properly tagged, so that one could locate them easily...
You are right about the license.  I hadn&#039;t spent much time reading license terms when I started the blog. CC was the first I read about, it suited my needs, so I used that one. GFDL is a good option and I was also thinking about &lt;a href=&quot;http://opencontent.org/openpub/&quot; rel=&quot;nofollow&quot;&gt;OPL&lt;/a&gt;. Hopefully, it will not require much manual editing, since the license info is added automatically by a plugin. :-)</description>
		<content:encoded><![CDATA[<p>I guess I was too lazy to create separate posts for each one of them, but certainly it would be better to have them properly tagged, so that one could locate them easily&#8230;</p>
<p>You are right about the license.  I hadn&#8217;t spent much time reading license terms when I started the blog. CC was the first I read about, it suited my needs, so I used that one. GFDL is a good option and I was also thinking about <a href="http://opencontent.org/openpub/" rel="nofollow">OPL</a>. Hopefully, it will not require much manual editing, since the license info is added automatically by a plugin. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Db0</title>
		<link>http://www.g-loaded.eu/2006/04/08/linux-tips-pack-i/#comment-716</link>
		<dc:creator>Db0</dc:creator>
		<pubDate>Fri, 28 Apr 2006 16:42:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.g-loaded.eu/2006/04/08/linux-tips-pack-i/#comment-716</guid>
		<description>Nice tips but I think it would be best if you posted them separately and used appropriate tags for each.
Just an idea.
PS: I think the GFDL is a better license for such information instead of the creative commons</description>
		<content:encoded><![CDATA[<p>Nice tips but I think it would be best if you posted them separately and used appropriate tags for each.<br />
Just an idea.</p>
<p>PS: I think the GFDL is a better license for such information instead of the creative commons</p>
]]></content:encoded>
	</item>
</channel>
</rss>

