<?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: Design Patterns in System Administration</title>
	<atom:link href="http://www.protocolostomy.com/2008/08/03/design-patterns-in-system-administration/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.protocolostomy.com/2008/08/03/design-patterns-in-system-administration/</link>
	<description>Made with only the finest 1's and 0's</description>
	<lastBuildDate>Thu, 26 Jan 2012 21:20:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Steve Loughran</title>
		<link>http://www.protocolostomy.com/2008/08/03/design-patterns-in-system-administration/comment-page-1/#comment-3140</link>
		<dc:creator>Steve Loughran</dc:creator>
		<pubDate>Fri, 29 Aug 2008 07:55:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/?p=348#comment-3140</guid>
		<description>I&#039;m building a &#039;patterns of deployment&#039; wiki, where deployment==the act of getting a working system up and running. The focus is mostly on CM-tool deployment (and java apps). And, patterns-style, it likes to look at the disadvantages of various approaches too: http://wiki.smartfrog.org/wiki/display/sf/Patterns+of+Deployment</description>
		<content:encoded><![CDATA[<p>I&#8217;m building a &#8216;patterns of deployment&#8217; wiki, where deployment==the act of getting a working system up and running. The focus is mostly on CM-tool deployment (and java apps). And, patterns-style, it likes to look at the disadvantages of various approaches too: <a href="http://wiki.smartfrog.org/wiki/display/sf/Patterns+of+Deployment" rel="nofollow">http://wiki.smartfrog.org/wiki/display/sf/Patterns+of+Deployment</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julian Simpson</title>
		<link>http://www.protocolostomy.com/2008/08/03/design-patterns-in-system-administration/comment-page-1/#comment-2938</link>
		<dc:creator>Julian Simpson</dc:creator>
		<pubDate>Wed, 20 Aug 2008 09:55:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/?p=348#comment-2938</guid>
		<description>Have you read this book? http://www.intel.com/intelpress/sum_book2.htm

I found it really interesting: an attempt to address the lack of patterns in infrastructure design.  It really only scratches the surface by describing things like n-tier designs.  But it&#039;s a start.

Great blog post, BTW!</description>
		<content:encoded><![CDATA[<p>Have you read this book? <a href="http://www.intel.com/intelpress/sum_book2.htm" rel="nofollow">http://www.intel.com/intelpress/sum_book2.htm</a></p>
<p>I found it really interesting: an attempt to address the lack of patterns in infrastructure design.  It really only scratches the surface by describing things like n-tier designs.  But it&#8217;s a start.</p>
<p>Great blog post, BTW!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: m0j0</title>
		<link>http://www.protocolostomy.com/2008/08/03/design-patterns-in-system-administration/comment-page-1/#comment-2667</link>
		<dc:creator>m0j0</dc:creator>
		<pubDate>Mon, 04 Aug 2008 16:59:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/?p=348#comment-2667</guid>
		<description>TPOSANA is a great timeless tome for system administrators. I read the first version all the way through, but I haven&#039;t yet made it through volume two. As for your point about the paradox between open software and closed network designs, I&#039;ve often wondered the same thing. Certainly lots of people are under a blanket of secrecy put on them by their employer. In other cases, it&#039;s a matter of specialization: in a LOT of places, no single person really knows all there is to know. 

As for not wanting to expose badness, I tend to find two trends: 

1. People readily talk about badness in the hopes that someone can give them a clue about how to make it better, or

2. The people I&#039;m talking to (clients, usually) don&#039;t even know the badness exists, otherwise it might not!</description>
		<content:encoded><![CDATA[<p>TPOSANA is a great timeless tome for system administrators. I read the first version all the way through, but I haven&#8217;t yet made it through volume two. As for your point about the paradox between open software and closed network designs, I&#8217;ve often wondered the same thing. Certainly lots of people are under a blanket of secrecy put on them by their employer. In other cases, it&#8217;s a matter of specialization: in a LOT of places, no single person really knows all there is to know. </p>
<p>As for not wanting to expose badness, I tend to find two trends: </p>
<p>1. People readily talk about badness in the hopes that someone can give them a clue about how to make it better, or</p>
<p>2. The people I&#8217;m talking to (clients, usually) don&#8217;t even know the badness exists, otherwise it might not!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew</title>
		<link>http://www.protocolostomy.com/2008/08/03/design-patterns-in-system-administration/comment-page-1/#comment-2666</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Mon, 04 Aug 2008 16:51:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.protocolostomy.com/?p=348#comment-2666</guid>
		<description>Practice of System and Network Administration is probably the best book out there for this. While it doesn&#039;t give exact how-to instructions, it is a great general resource for Systems Administrators. I would have loved this book if I had discovered it in the early days of my career.

http://www.amazon.com/Practice-System-Network-Administration-2nd/dp/0321492668/ref=pd_bbs_sr_1?ie=UTF8&amp;s=books&amp;qid=1217868163&amp;sr=8-1

Something I have been wondering about is why we like to Open Source our software, but then treat our networks as proprietary information. Security? Shame? Laziness?

- A.</description>
		<content:encoded><![CDATA[<p>Practice of System and Network Administration is probably the best book out there for this. While it doesn&#8217;t give exact how-to instructions, it is a great general resource for Systems Administrators. I would have loved this book if I had discovered it in the early days of my career.</p>
<p><a href="http://www.amazon.com/Practice-System-Network-Administration-2nd/dp/0321492668/ref=pd_bbs_sr_1?ie=UTF8&#038;s=books&#038;qid=1217868163&#038;sr=8-1" rel="nofollow">http://www.amazon.com/Practice-System-Network-Administration-2nd/dp/0321492668/ref=pd_bbs_sr_1?ie=UTF8&#038;s=books&#038;qid=1217868163&#038;sr=8-1</a></p>
<p>Something I have been wondering about is why we like to Open Source our software, but then treat our networks as proprietary information. Security? Shame? Laziness?</p>
<p>- A.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

