<?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 of the UNIX Operating System (Prentice Hall Software Series) (Paperback)</title>
	<atom:link href="http://unix.computers-n-internet.com/topic_reviews/2009070518.html/feed" rel="self" type="application/rss+xml" />
	<link>http://unix.computers-n-internet.com/topic_reviews/2009070518.html</link>
	<description>Unix ~  Working To Be A Practical Guide to the UNIX System</description>
	<lastBuildDate>Wed, 21 Apr 2010 21:23:01 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Etan</title>
		<link>http://unix.computers-n-internet.com/topic_reviews/2009070518.html/comment-page-1#comment-43</link>
		<dc:creator>Etan</dc:creator>
		<pubDate>Mon, 06 Jul 2009 01:44:34 +0000</pubDate>
		<guid isPermaLink="false">http://unix.computers-n-internet.com/topic_articles/2009070518.html#comment-43</guid>
		<description>&lt;/div&gt;

Maurice Bach&#039;s The Design of the Unix Operating System still holds the place of honor on my technical reference bookshelf.  After almost 20 years, it provides a clear overview of basic Unix organization and operations and is a model for how technical books should be written.  Readers who complain that the text is dated evidently did not bother to notice the 1986 copyright date.  Its age, however, has not diminished its clarity of content or usefulness in understanding the Unix operating system. Bach deserves an award for excellence in technical writing.
      </description>
		<content:encoded><![CDATA[<p>Maurice Bach&#8217;s The Design of the Unix Operating System still holds the place of honor on my technical reference bookshelf.  After almost 20 years, it provides a clear overview of basic Unix organization and operations and is a model for how technical books should be written.  Readers who complain that the text is dated evidently did not bother to notice the 1986 copyright date.  Its age, however, has not diminished its clarity of content or usefulness in understanding the Unix operating system. Bach deserves an award for excellence in technical writing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bailey</title>
		<link>http://unix.computers-n-internet.com/topic_reviews/2009070518.html/comment-page-1#comment-42</link>
		<dc:creator>Bailey</dc:creator>
		<pubDate>Sun, 05 Jul 2009 23:05:13 +0000</pubDate>
		<guid isPermaLink="false">http://unix.computers-n-internet.com/topic_articles/2009070518.html#comment-42</guid>
		<description>&lt;/div&gt;

After becoming a Linux enthusiast, I bought the book &quot;Understanding the Linux Kernel&quot;, which I unfortunately found to be almost completely impenetrable.  I had heard good things about this book (&quot;The Design of the UNIX Operating System&quot;) - in fact, I read somewhere that this was the book that taught Linus to write OS code.  I put down the Linux book and picked up Maurice Bachs, which I found perfectly readable - it&#039;s abstract treatment of kernel algorithms made it easy to get the &quot;big picture&quot;.  Now, with Bach&#039;s complete treatment of the design philosophy under my belt, I&#039;m going back to the linux kernel book, and I&#039;ve found it to be a breeze... even the linux kernel source code itself now makes sense.  This book is excellent for anybody who&#039;s serious about programming.
      </description>
		<content:encoded><![CDATA[<p>After becoming a Linux enthusiast, I bought the book &#8220;Understanding the Linux Kernel&#8221;, which I unfortunately found to be almost completely impenetrable.  I had heard good things about this book (&#8221;The Design of the UNIX Operating System&#8221;) &#8211; in fact, I read somewhere that this was the book that taught Linus to write OS code.  I put down the Linux book and picked up Maurice Bachs, which I found perfectly readable &#8211; it&#8217;s abstract treatment of kernel algorithms made it easy to get the &#8220;big picture&#8221;.  Now, with Bach&#8217;s complete treatment of the design philosophy under my belt, I&#8217;m going back to the linux kernel book, and I&#8217;ve found it to be a breeze&#8230; even the linux kernel source code itself now makes sense.  This book is excellent for anybody who&#8217;s serious about programming.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fielding</title>
		<link>http://unix.computers-n-internet.com/topic_reviews/2009070518.html/comment-page-1#comment-41</link>
		<dc:creator>Fielding</dc:creator>
		<pubDate>Sun, 05 Jul 2009 16:03:37 +0000</pubDate>
		<guid isPermaLink="false">http://unix.computers-n-internet.com/topic_articles/2009070518.html#comment-41</guid>
		<description>&lt;/div&gt;

UNIX in its many derivatives is a 30-year old operating system.  Why has it stood the test of time?  Because it was designed with a simple philosophy:  to give the user the ability to create his own tools to solve problems.  This book has been a classic in UNIX architecture since it was published in 1987.  Although some of the sections are a bit dated (e.g., IPC, file systems), it is still a valuable source of information.  You will begin to understand the design philosophy of UNIX after reading this book.  You will see why some of the design decisions were made (primarily due to the hardware of the time) and some of the really neat kluges that was devised to get around those problems.  This book deserves its status as one of classics of UNIX literature.  I highly recommend it.
      </description>
		<content:encoded><![CDATA[<p>UNIX in its many derivatives is a 30-year old operating system.  Why has it stood the test of time?  Because it was designed with a simple philosophy:  to give the user the ability to create his own tools to solve problems.  This book has been a classic in UNIX architecture since it was published in 1987.  Although some of the sections are a bit dated (e.g., IPC, file systems), it is still a valuable source of information.  You will begin to understand the design philosophy of UNIX after reading this book.  You will see why some of the design decisions were made (primarily due to the hardware of the time) and some of the really neat kluges that was devised to get around those problems.  This book deserves its status as one of classics of UNIX literature.  I highly recommend it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
