<?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: Seagate isolates &#8216;potential&#8217; Barracuda flaw</title>
	<atom:link href="http://www.lexum.ru/2009/01/18/seagate-isolates-potential-barracuda-flaw/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lexum.ru/2009/01/18/seagate-isolates-potential-barracuda-flaw/</link>
	<description>+7 905-710-11-12</description>
	<lastBuildDate>Thu, 22 Apr 2010 00:54:21 +0300</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Seagate isolates ‘potential’ Barracuda flaw &#124; DataRecovery</title>
		<link>http://www.lexum.ru/2009/01/18/seagate-isolates-potential-barracuda-flaw/comment-page-1/#comment-29</link>
		<dc:creator>Seagate isolates ‘potential’ Barracuda flaw &#124; DataRecovery</dc:creator>
		<pubDate>Sun, 18 Jan 2009 07:40:08 +0000</pubDate>
		<guid isPermaLink="false">http://lexum.ru/2009/01/18/seagate-isolates-potential-barracuda-flaw/#comment-29</guid>
		<description>[...] here: Seagate isolates ‘potential’ Barracuda flaw   Share and [...]</description>
		<content:encoded><![CDATA[<p>[...] here: Seagate isolates ‘potential’ Barracuda flaw   Share and [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

