2. Samba-3 By Example 2nd Ed.

Practical Exercises to Successful Deployment

2.1 4/5 Recommended for the Experienced User

John H. Terpstra
2006, John H. Terpstra, ISBN 0-13-188221-X
$44.99 USD

2.2  Overview

This is the 2nd Edition to an already very good book. Enough changes have happened in Samba 3 that could not be covered in the 1st Edition. This is a timely and welcome update. By the way, the techniques used in publishing these books makes it possible to rapidly get new books out while the technology is still relevant. This book, for example, covers 3.0.20 and later of Samba. The latest version of Samba 3 as of this writing is 3.0.20b. That's incredible. My compliments to the contemporary editing techniques used on these books. Everyone doing technical publishing should switch!

This book attempts to simulate real life examples with fictitious companies and scenarios to demonstrate how to configure Samba. Well... at least for the first part of the book anyhow. The rest is devoted to information that will help you further with configuration and troubleshooting.

2.3  Welcome to Abmas!

Abmas, the fictitious company in the examples, slowly matures and changes and faces challenges that involve Unix/Linux and Windows. It start off with a basic configuration that might work at a very small company or at home. Then it moves to a small-medium sized business example and finally, to a more complex scenario. The problem: Not every scenario is covered. Which isn't necessarily a bad thing, but there are just so many variations that it would be difficult to cover everything.

2.4  Outside Reading Required

Samba by Example is not a complete text. What I mean is that some of the information in the book, for example LDAP, will require information and experience outside of this book. Again, that might not be a bad thing... but perhaps a bit frustrating for the beginner and even intermediate user.

2.5  What I Liked

I like the example format. It makes the reading fun. Also, the question/answer section at the end of the chapters a fun... but perhaps a bit contrived. The Q&A is useful, just not what you might expect if you thought of this book as a potential textbook. I like the two part nature of the book where it leaves the example scenarios and moves into information that is useful for troubleshooting.

2.6  What I Didn't Like

Book simply doesn't cover some complex matters even when the chapters are totally dependent on those technologies. To fix this would mean increasing the size of this text dramatically. Maybe that's the wrong answer. I don't know.

I also don't like the fact that most of the scenarios take a pro-Samba position. There are a few cases where it it mentioned that Windows is already present in a Domain role, but most of the time, it is assumed that Samba is king of the network. Again, this isn't a bad idea... just not found in a typical workplace. For example, I live on a mature NIS infrastructure. We use Samba-3 to authenticate, but we map the users between Windows and NIS. Certainly Microsoft does provide a way of letting Microsoft control a NIS domain, but that's pretty silly when you think about it. Anyhow, for me, it lacked specific scenarios that are closer to my own situation.

2.7  Conclusion

This is a great book! If you are just getting started, especially in a situation where Microsoft Domains are not employed yet, this book is invaluable! Because some required concepts are not covered adequately, I do recommend this more for an experienced administrator (especially with LDAP experience) that is somewhat new to Samba or implementing a new Samba installation.

4. Moving to Linux 2nd Ed.

4.1 4/5 Recommended for the newbie

Marcel Gagné
2006, Pearson Education, Inc, ISBN 0-321-35640-3
$39.99 USD

4.2  The First Few Chapters

Walk into a computer software store and you'll see copies of Mandrake, SuSE, and Red Hat ... you can buy Red Hat personal or professional edition.

Simple mistakes, but ones that should have been caught. It's Mandriva now. It's SUSE now. And Red Hat, well, you do not see their boxed version often, and when you do, they will be the Red Hat Enterprise Linux WS or Red Hat Desktop editions. These are the kind of things that have changed from the 1st edition to the 2nd edition. Somebody should have caught this. In all fairness, Marcel does mention that he intentionally chose to use the name Mandrake throughout the book, even though in one aside he speaks of the merger with Connectiva and the new name. I'm not sure I believe that was the actual reason (it is not convincing to me). On that same page with the aside, SuSE is correctly represented as SUSE ... again, I think some items were simply missed.

Another minor nit is the font used on the start page of each chapter. It is hideous. Fortunately, it's usually just a small paragraph. But this is something easily changed and in my opinion should be changed. Maybe I'm just looking at things through 40 year old eyes.

I like the fact that the author points out that while Linux may not support all hardware devices, it does come with drivers, something that other operating systems cannot do. On Windows for example, you buy hardware and install the vendor's driver. On Linux, the driver is usually either there or not there. You seldom have to go and track down drivers in Linux.

I also liked the fact that he directs people to get involved with a local Linux User Group (LUG). You local LUG is truly your best source of support for Linux.

This book comes with a Knoppix variant live CD. It's called WFTL Knoppix after Marcel's local LUG, WFTL (Writer and Free Thinker at Large). He also has a website that might help with some things. It is at http://www.marcelgagne.com .

He recommends younger wines over older ones. While this is generally true, it is also true that last week's wine may be much, much better than this week's. Sometimes, last year's wine is better. When I give talks on wine, I warn people that it is very much like real wine. Some vintages are excellent. Age is not the best indicator.

4.3  Dirtying Your Hands

After talking about logging in and doing a cursory walk around KDE, he discusses a little about package installation. I can appreciate the fact that he covers things like YaST and urpmi, but once again, like so many others, he tells you that Debian packages and the urpmi installer handle dependencies ... and he implies that YaST does not. However, YaST does do dependency checking and will install dependent packages. Apart from this, I found most of the introductory information very accurate and useful.

When talking about networking applications, he makes a plea for jabber! How refreshing. It's nice to know that the author knows why open standards such as Jabber are better than the countless other instant messaging (IM) servers. Good job!

4.4  Productivity Applications

When going through OpenOffice Writer, Marcel mentions the fact that the book itself was written using OpenOffice. That should speak volumes for those wondering if OpenOffice can handle "real" work. In fact portions were written with a beta 2.0 copy. Very nice.

About the only problem I found here was with regards to gimp. Gimp is a vector drawing package and the author does a great job of helping the new user to know the basics of this very powerful package. Gimp is such a powerful and complicated tool, I'm not sure if I would have attempted this in a beginner text. I guess I should not be so critical. He actually does about the best job I've seen in trying to make a complicated tool simple and immediately useful.

4.5  Games

Personally, if you own a computer and do not use it for games, you are wasting money. I'm glad that Marcel ended the book with a sizable chapter on games for Linux. Nice, large screenshots give you a good feeling about the games he mentions in the book.

4.6  End Matter

The appendices are great! Includes a copy of the GNU Public License (GPL). Has a large appendix covering some shell basics. A brief one on editors... where he says the most important word, "vimtutor."

4.7  Recommended for Beginners

This is not a bad book at all for beginner's. In my opinion the 3rd Edition could get perfect marks with just a few corrections here and there.

6.  Peter van der Linden's Guide to Linux

6.1 2/5 Pass on This

Peter van der Linden
2006, Prentice Hall, ISBN 0-13-187284-2
$39.99 USD

6.2  Overview

There are plethora of introductory books on Linux just like any other computing topic. For example, suppose you want to know everything about HTML. You have rooms full of books to choose from. So which one do you choose? If you are a bargain hunter, you just find the $1.00 special. Maybe it's good enough... if not, it at least gets you started. When I first started reading this book... I felt I was reading that bargain basement quality text.

Especially early in this book the author makes many unsubstantiated claims, makes many, many, many, many, many "digs" at Microsoft and it just leaves you feeling that the author knows everything! The good news is that the latter half of the book is better written, though perhaps it contains a bit too much technical detail for a book targetting a non-technical audience.

I have read better discount books.

6.3  Preface

"As long as you have a PC that runs 800Mhz or more, with at least 256M memory, you're good to go."

Hmmm... the fact is that Linux runs on many platforms with much less... even today. The author fails to identify that these may well be the requirements of Linspire 5.0, but when you consider that my wireless router, a Linksys WRT54G, is running Linux, clearly this is not a true statement without some sort of qualification. But do not look for that qualification or even an explanation inside of this book. It makes statements, true ones and false ones, but you will not know the reasoning behind the statements, all is presented as being "true"... Why is it true? Apparently because Peter van der Linden says so.

6.4  About the Author

Let's face it, the guy's brief bio reads like any of the "gods" of geekdom. "For the last twenty years he has worked in Silcon Valley, for Sun Microsystems, Apple Computers, a storage start-up, and everything in between." He has written "Expert C Programming" and his "Just Java" was twice nominated for Java Book of the Year. "He gets a real kick out figuring out how things work, and explaining them more clearly than anyone else." I would like to make a small edit to that last quote from the book. In my honest opinion it should read, "He believes he can figure anything out and knows for sure that anything he writes is better than anyone else". That's my impression of his writing anyway. This book does contain some good material, but you do have to put up with many opionated asides and the occasional unsubstantiated "fact".

6.5  Hello Linux

"For several years, Windows was adequate for Josh. But lately, his system ran slower than it used to. He could see the modem 'in use' light flickering when he wasn't doing anything. Josh noticed that his virus protection software had somehow been disabled. Was someone interfering with his computer from across the Internet? When Josh discovered his password had been changed from under him, he called me for help.

Does any of this story sound familiar? With Linux, these Windows woes disappear completely."

While it is certainly true that Linux CAN be safer to use than Windows, it is still a tool that needs to be understood administratively, the same as any other network operating system, before many "woes" are dealt with. And even then, no one, NO ONE, should ever say, "With Linux, these Windows woes disappear completely."

"Since all current viruses spread automatically, the two terms virus and worms are synonymous these days."

The truth is that most virus infections are still loaded with the help of the end user. I am not saying that there are not remotely exploitable holes in Windows, but still, the most common way that a virus is spread is with user assistance, often times in the form of opening up an attachment that carries a virus payload.

"At work, you probably have fewer problems with Windows viruses. At work, there should be computer staff paid to look for and block viruses, to keep up-to-date with security software patches, to notice and solve problems before they get out of hand, and to make backup copies of vital data. Few users want to spend time and money taking the same precautions at home. Nor should we have to -- other operating systems don't have these problems."

Some very idealistic statements are made here, but I must take issue with the last statement. Other operating systems, even Linux CAN have these exact same problems. The benefits of Linux are in the knowledge and education that come with it. Linux users tend to be more educated and therefore, the chance that you will download and execute a malicious program are lessened, but certainly still possible. I had the displeasure of doing a post mortem on a hacked Linux computer. The computer was running Red Hat 6.0 (I think I just heard a loud "Ugh!") and it was root kitted. The root kit identified itself and it even had a copy of itself (the installer was very user friendly but full of bad language) just in case it need to be reinstalled. There was a cron job that checked and reinstalled it if necessary. Now, in all fairness, not all root kits are so friendly. This one certainly announced itself rather loudly. The reason it went months and months without being detected was because the administrators probably believe that "other operating systems don't have [the] problems [of Windows]."

I redesigned their infrastructure to make it more resistent to attack. It did mean taking away quite a bit of functionality. Functionality they have NO business having without a full time administrator (something that they lack). I still check on that infrastructure from time to time. It is still secure (meaning not hacked). But I will not kid myself into thinking that it's impervious because it is running Linux.

Oddly enough, Appendix A, "Malicious Windows Software", give a more honest treatment of the subject matter. Indeed this book seems to have two parts. Silly and serious.

"Every time you place a bid on eBay, you are using servers at eBay that run Linux."

That could be true. I do not know. However I do know that eBay says about itself, and I would think they'd know better than the author:

 eBay is Java™ Powered
 Running on powerful Sun Solaris™ SPARC® servers
 Supported by Sun services and solutions

 eBay has chosen Sun’s Solaris Operating System, the most
 advanced operating system on the planet and its Solaris
 servers and Java software to help power The World’s Online
 Marketplace. If you’re running a  business like eBay’s, or have
 similar aspirations, get some Sun.

http://sun.ebay.com/odcs/custom.htm?template=popup

So according to eBay, they use Sun Solaris. With that said, it's possible that there are still Linux hosts within the eBay infrastructure. I'm just telling you what eBay says. This information, by the way was present way before publication of this book. In the past, eBay used IBM's WebSphere using a combination of Microsoft Windows, Linux and Solaris. Is Linux still there? Perhaps. But the only thing that eBay wants you to know is that they run Solaris with Java technology.

One of my favorites:

"The city of Munich, Germany, is switching all of its 14,000 desktops to Linux. If non-technical council workers can switch to Linux, you can too."

(you may read into that statement yourself!)

Drivers? Not a problem... well... a problem.. no.. wait, not a problem.. but yes, a problem. BUT, you can blame it all on "the CEO of notorious Linux laggard Texas Instruments", that being Tom Engibous... snail mail address is in the book. I'm sure Tom appreciates the mention! Funny, Texas Instruments probably would not have been my first pick (and Peter's ONLY pick) with regards to poor integration with Linux. I just looked at the T.I. web site. Apart from Tom, I didn't recognize the other names of the executives. Tom has been there a long time. He was there when I was there between 1985-90. I don't think it was appropriate to single out Tom and T.I. the way the author did.

6.6  Into the Meat of the Book

Fortunately we're out of the woods with regards to the misinformation and highly opionated, and often charged statements by Mr. van der Linden, right? Nope. Any chance he gets, he takes aim and fires. Usually without substantiation (did I say usually?... I don't know if he ever backs up anything he says).

The KDE Desktop

KDE is the desktop of choice in Linspire. But there are some pretty glaring mistakes in the text. For example, on a section describing how to change to a different "folder" inside of the Konqueror browser, the caption on the screenshots is labeled "Moving Konqueor to a new location." That's a very confusing statement. The secton is titled "Moving Konqueor to Display a Different Folder," which is not that much better, but definitely better. Why not use that for the caption? This may just be an editing mistake of course.

With regards to using Windows folders from your Windows partitions, he states correctly that you might not be able to reliably write to NTFS. This is true. But is the following true? "Microsoft keeps secret the details of its NTFS file system to hinder Linux people working for greater interoperability." I did not know that was the main reason why NTFS details were being kept secret. I just figured that Microsoft kept it secret because they believe that "Intellectual Property" is defined by that which is inherently kept secret (an idealogy that I personally believe is flawed).

Onto the Net

One of my favorites from this section is the probabilities list that your network choice will work with Linux: "Somewhat more than 0% that a dial-up modem will just work. But perhaps not a whole lot more than zero. All modems that contain true modem hardware will work fine. But the most common modems today are cheap and nasty Winmodems, which rely on Windows-only software to operate." Don't get me wrong. I do not like those "nasty Winmodems" either. But the truth is that many are now supported in Linux. Nasty? :)

Several paragraphs detail out the problems caused by not having your broadband modem plugged in. You'll learned that the best way to test your connectivity is by trying to browse to google.com. You'll learned that if that doesn't work, you don't have a working network connection. :)

As an aside. This book is written for stupid Americans (but obviously smarter than Munich council workers). I say this because the examples are targeted from a USA point of view. This is especially true in the network section where the examples will differ greatly in other regions of the world. This is not the only book that has this limitation though.

6.7  Book Gets Better

The chapters detailing more about Linspire and package management and brief tutorials on various applications are actually pretty good. There's less unsubstantiated claims, less slamming of Microsoft... he actually tells you some things that are interesting. In fact, he even goes into greater detail about protocols and formats... which is interesting since that would qualify as support "substance". I guess there are some resonable chapters in the text after all. But I found quite a bit of it to be humorous... but in a sad way.

Unfortunately the "better" parts don't last long, and we quickly find ourselves in the chapter dealing with Windows share/network connectivity... and more of the anti-Microsoft rhetoric I have come to enjoy! Fortunate for us, Peter is one of the few people that "read the Microsoft support bulletins" and he figures most will find out about a particular flaw in WinXP SP2 when "their systems are penetrated." There is a whole lot of arrogance expressed throughout this book.

6.8  Conclusion

There is some good information in this book. However, I felt that some of the better parts contained perhaps too much technical detail. But, the more introductory sections of the book, especially early on, contain too much unsubstantiated claims and opinion.

The book is barely "ok" IMHO. You can do much better than this one.