<?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: InsideTrack: Letter from SGI to LNXI customers</title>
	<atom:link href="http://insidehpc.com/2008/02/19/insidetrack-letter-from-sgi-to-lnxi-customers/feed/" rel="self" type="application/rss+xml" />
	<link>http://insidehpc.com/2008/02/19/insidetrack-letter-from-sgi-to-lnxi-customers/</link>
	<description>HPC News Without the Noise for Supercomputing Professionals &#124; insideHPC</description>
	<lastBuildDate>Sun, 19 May 2013 10:46:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
	<item>
		<title>By: sharan kalwani</title>
		<link>http://insidehpc.com/2008/02/19/insidetrack-letter-from-sgi-to-lnxi-customers/#comment-36464</link>
		<dc:creator>sharan kalwani</dc:creator>
		<pubDate>Fri, 22 Feb 2008 15:29:05 +0000</pubDate>
		<guid isPermaLink="false">http://insidehpc.com/2008/02/19/insidetrack-letter-from-sgi-to-lnxi-customers/#comment-36464</guid>
		<description>Going thru this week&#039;s hpcwire.com

 I noticed that LNXI still advertises on  the right hand side of the website (all over the place). Should they not at least remove it (or gray it out? ;-)or if SGI is willing, occupy two slots or forward it to sgi.com instead of the old lnxi.com?</description>
		<content:encoded><![CDATA[<p>Going thru this week&#8217;s hpcwire.com</p>
<p> I noticed that LNXI still advertises on  the right hand side of the website (all over the place). Should they not at least remove it (or gray it out? <img src='http://insidehpc.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> or if SGI is willing, occupy two slots or forward it to sgi.com instead of the old lnxi.com?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
