<?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: Looking For Network/Direct Attached Storage</title>
	<atom:link href="http://conigliaro.org/2007/11/25/looking-for-networkdirect-attached-storage/feed/" rel="self" type="application/rss+xml" />
	<link>http://conigliaro.org/2007/11/25/looking-for-networkdirect-attached-storage/</link>
	<description>cat /dev/brain &#124; grep technology &#62;&#62; blog</description>
	<lastBuildDate>Wed, 01 Sep 2010 20:51:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Brandon</title>
		<link>http://conigliaro.org/2007/11/25/looking-for-networkdirect-attached-storage/comment-page-1/#comment-86</link>
		<dc:creator>Brandon</dc:creator>
		<pubDate>Sat, 19 Jul 2008 18:22:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.gyrate.org/2007/11/25/looking-for-networkdirect-attached-storage/#comment-86</guid>
		<description>I&#039;ve been thinking about this a lot lately. The problem with these bloated solutions is that they are way too expensive for what they are. A raid controller, network card, perhaps a custom board for managing a few hd state leds, an almost silly administration interface that never has all the features you want, and an enclosure. At first I didn&#039;t see why it was necessary to spend so much more for simply taking an operating system out of the picture.

But on the other side, an os requires a bit more in the way of hardware and configuration, which is why most people would prefer to just throw money at the problem. So what to do? Spend an assload on someone else&#039;s plug and play solution, or build a fileserver and call it a day?

I think neither. Personally, I&#039;d rather develop my own solution. The problem is, essentially, managing a stack of raided drives(backups, notification of drive space limits and failures), connecting them to a network, having a good set of tools to set permissions and the like, and not breaking the bank. An enclosure, stripped down hardware, a lamp install, and a bit of time is all that should be necessary. And more likely than not, even with money lost on a raid card or motherboard that doesn&#039;t work out, the price will more than likely end up under 1k. We&#039;ll see.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been thinking about this a lot lately. The problem with these bloated solutions is that they are way too expensive for what they are. A raid controller, network card, perhaps a custom board for managing a few hd state leds, an almost silly administration interface that never has all the features you want, and an enclosure. At first I didn&#8217;t see why it was necessary to spend so much more for simply taking an operating system out of the picture.</p>
<p>But on the other side, an os requires a bit more in the way of hardware and configuration, which is why most people would prefer to just throw money at the problem. So what to do? Spend an assload on someone else&#8217;s plug and play solution, or build a fileserver and call it a day?</p>
<p>I think neither. Personally, I&#8217;d rather develop my own solution. The problem is, essentially, managing a stack of raided drives(backups, notification of drive space limits and failures), connecting them to a network, having a good set of tools to set permissions and the like, and not breaking the bank. An enclosure, stripped down hardware, a lamp install, and a bit of time is all that should be necessary. And more likely than not, even with money lost on a raid card or motherboard that doesn&#8217;t work out, the price will more than likely end up under 1k. We&#8217;ll see.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
