<?xml version="1.0" encoding="UTF-8"?><!-- generator="lyceum/1.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Book review:  Fedora 7 Unleashed</title>
	<link>http://www.redhatmagazine.com/2007/11/01/book-review-fedora-7-unleashed/</link>
	<description>Red Hat Magazine</description>
	<pubDate>Mon,  6 Oct 2008 18:53:46 +0000</pubDate>
	<generator>http://lyceum.ibiblio.org/?v=1.0.2</generator>

	<item>
		<title>by: Dean Espaillat</title>
		<link>http://www.redhatmagazine.com/2007/11/01/book-review-fedora-7-unleashed/#comment-31760</link>
		<pubDate>Fri, 09 Nov 2007 04:31:20 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2007/11/01/book-review-fedora-7-unleashed/#comment-31760</guid>
					<description>Tonight I went to my favorite book store and carefully looked over 10 or so books for two hours only to be disappointed as usual.  This was one of the books I looked over.  I do this about once a year and I am always disappointed.  I would love to see a book that leverages new tools and distros to build a best practices network of Linux systems and describes the best way to manage them. All these books focused on one or two systems at a time.  I suppose that might be useful it I had one or two Linux systems, but it doesn't help me determine the best way to manage many systems.  I'm left wondering what kool stuff is going on behind the closed doors of other medium to large Linux networks.</description>
		<content:encoded><![CDATA[<p>Tonight I went to my favorite book store and carefully looked over 10 or so books for two hours only to be disappointed as usual.  This was one of the books I looked over.  I do this about once a year and I am always disappointed.  I would love to see a book that leverages new tools and distros to build a best practices network of Linux systems and describes the best way to manage them. All these books focused on one or two systems at a time.  I suppose that might be useful it I had one or two Linux systems, but it doesn&#8217;t help me determine the best way to manage many systems.  I&#8217;m left wondering what kool stuff is going on behind the closed doors of other medium to large Linux networks.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Brad Scalio</title>
		<link>http://www.redhatmagazine.com/2007/11/01/book-review-fedora-7-unleashed/#comment-30662</link>
		<pubDate>Sat, 03 Nov 2007 11:59:19 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2007/11/01/book-review-fedora-7-unleashed/#comment-30662</guid>
					<description>The very first RedHat book I owned was an unleashed edition of RedHat Linux 5.  I was thrusted into a SysAdmin position as my company transition from HPUX to Gnu/Linux because I was the only one who ever heard of Linux, and I happend to run it on my desktop.

I can't remember ever reading the book, in the sense one reads a novel.  I do however remember feeling a slight sense of security with a 1,000 page reference guide on my shelf overtop my workstation. 

I have been a Gnu/Linux user now for 10 years, and as my career grew so did my collection of specific books on topics such as Bash, Perl, etc ... but I still have that first unleashed (can't seem to throw it away even though it is outdated).  I notice as I go into other folks offices a different version of some comprehensive OS book adorning their shelf as well, be it O'Reily, Unleashed, etc ... but it seems at some point everyone owned/owns one of these for al the derision we give them.

I would appreciate some reviews of more low-level books, like a kernel internals book and a side by side comparison of what ones you find most useful because face it, googling things are great for your immediate sysadmin/troubleshooting duties...but when it comes time to write modules I still don't fully trust google for the deep understanding of what you are doing.  It is a great source for commands and how-tos, but the WHY is often missing...which is where these books fill out.

</description>
		<content:encoded><![CDATA[<p>The very first RedHat book I owned was an unleashed edition of RedHat Linux 5.  I was thrusted into a SysAdmin position as my company transition from HPUX to Gnu/Linux because I was the only one who ever heard of Linux, and I happend to run it on my desktop.</p>
<p>I can&#8217;t remember ever reading the book, in the sense one reads a novel.  I do however remember feeling a slight sense of security with a 1,000 page reference guide on my shelf overtop my workstation. </p>
<p>I have been a Gnu/Linux user now for 10 years, and as my career grew so did my collection of specific books on topics such as Bash, Perl, etc &#8230; but I still have that first unleashed (can&#8217;t seem to throw it away even though it is outdated).  I notice as I go into other folks offices a different version of some comprehensive OS book adorning their shelf as well, be it O&#8217;Reily, Unleashed, etc &#8230; but it seems at some point everyone owned/owns one of these for al the derision we give them.</p>
<p>I would appreciate some reviews of more low-level books, like a kernel internals book and a side by side comparison of what ones you find most useful because face it, googling things are great for your immediate sysadmin/troubleshooting duties&#8230;but when it comes time to write modules I still don&#8217;t fully trust google for the deep understanding of what you are doing.  It is a great source for commands and how-tos, but the WHY is often missing&#8230;which is where these books fill out.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Stephen Smoogen</title>
		<link>http://www.redhatmagazine.com/2007/11/01/book-review-fedora-7-unleashed/#comment-30389</link>
		<pubDate>Thu, 01 Nov 2007 23:10:54 +0000</pubDate>
		<guid>http://www.redhatmagazine.com/2007/11/01/book-review-fedora-7-unleashed/#comment-30389</guid>
					<description>One of the things that come up when writing a 'tome' book on technology is that editors want the book to be packed for important reasons.

1) Technology books have a store-shelf life of 6 months to 1 year. Most people buying such books do so on size of book and if they know what is in the book how much that book might help them after the OS is wiped out with FC-8/9/10.

2) A good portion of these books are sold to non-technical savy people who came home and found the home computer has some new OS on it when Billy goes abck to college. And Billy's instructions of 'look it up on Google' means zip to you. You market to this crowd with size. They could go for the 100 page NO BS Guide To Fedora's OR you could supersize it with the 1200 page Fedora BIBLE New, Old, and Apocryphal Edition. Most people will buy the bigger version because thats how the human brain works.

3) Fedora and Ubuntu do releases at extremely high rates so the authors do not have time to update/change things as much as they might like. So the publisher must make as much of the book stable so that you can basically reuse the chapters over and over again because they may only get one book sell in 3-4 releases (eg that guy who just bought Fedora Core 6 unleashed is going to not buy 7,8,9 unless something really major changed).

4) People selling books are selling them to people who do not like to read long times at computers or want to read them when 'cogitating'. There is a reason that many of these books are printed on 'toilet paper' stock. I find that these times of deep thinking are usually when I want a nice big book, and I want them to have lots of stuff. 

So anyway.. my take on big books.</description>
		<content:encoded><![CDATA[<p>One of the things that come up when writing a &#8216;tome&#8217; book on technology is that editors want the book to be packed for important reasons.</p>
<p>1) Technology books have a store-shelf life of 6 months to 1 year. Most people buying such books do so on size of book and if they know what is in the book how much that book might help them after the OS is wiped out with FC-8/9/10.</p>
<p>2) A good portion of these books are sold to non-technical savy people who came home and found the home computer has some new OS on it when Billy goes abck to college. And Billy&#8217;s instructions of &#8216;look it up on Google&#8217; means zip to you. You market to this crowd with size. They could go for the 100 page NO BS Guide To Fedora&#8217;s OR you could supersize it with the 1200 page Fedora BIBLE New, Old, and Apocryphal Edition. Most people will buy the bigger version because thats how the human brain works.</p>
<p>3) Fedora and Ubuntu do releases at extremely high rates so the authors do not have time to update/change things as much as they might like. So the publisher must make as much of the book stable so that you can basically reuse the chapters over and over again because they may only get one book sell in 3-4 releases (eg that guy who just bought Fedora Core 6 unleashed is going to not buy 7,8,9 unless something really major changed).</p>
<p>4) People selling books are selling them to people who do not like to read long times at computers or want to read them when &#8216;cogitating&#8217;. There is a reason that many of these books are printed on &#8216;toilet paper&#8217; stock. I find that these times of deep thinking are usually when I want a nice big book, and I want them to have lots of stuff. </p>
<p>So anyway.. my take on big books.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
