Linux Clustering
Bookman emphasizes a central piece of wisdom that no system administrator should ignore: redundancy. In the case of high availability clusters, parts redundancy is the name of the game, but one should not forget the human component; no administrator should be caught with only a cell phone -- keep a pager just in case. However, in a post-modern turn that might seem brilliant if it were applied in a work of fiction rather than a technical book, the author seems to apply the concept of redundancy to the text itself.
That the book began not as a book but rather as a collection of talks or presentations, or some other smaller format, is evidenced by the repetition of information between chapters and sections. Such nearly poetic repetitions also occurs within sentences and paragraphs (e.g. "nightly backups each night" on page 25).
An editor never looked at Linux Clustering; the book had two "technical reviewers" but their contributions seemingly didn't include fixing mangled syntax and strained style. On page 14 in the second paragraph a large segment of a sentence from the previous page is pasted into another sentence, resulting in a nonsensical block of text. The number of hyphenation, syntax, word choice, and subject-verb agreement errors is atrocious and makes the book difficult to read.
Some of the misinformation in the text appears to be unintentional (but ignorance is no excuse for a UNIX systems administrator); some is due to the fact that the author deals only with old (2.2) kernels (though the book came out 18 months after the 2.4 kernel release), old versions of journaling filesystems, and old distributions; and yet other misinformation is the result of misplaced attempts at humor (such as stating that GNU stands for the Gateway Naming Utility; one can only hope that this was intended to be funny). Other jokes often misfire, but do point to the intended audience (consider, for example, the section heading "Space: The Final Frontier").
In the Introduction, the author indicates that the book should be read by "Linux enthusiasts and users who want to get a Linux cluster up and running with the least amount of fuss." The organization of the book will not, however, aid this enterprise, for there is little "how to" information provided, but rather a great deal of background information on compiling kernels, various types of journaling file systems, and RedHat's Kickstart (perhaps inappropriate considering that the book specifically states that basic information will not be covered). Another section or two deal with basic networking and security. Various types of clusters are discussed, as are a few of the types of clustering software (e.g. Condor and Mosix) available.
The book, however, is clearly intended for administrators of clustering systems; a special emphasis is high-availability and load-balancing clusters. Parallel computing and the types of applications end users would wish to run receive far too little discussion.
Almost all technical books regurgitate the contents of freely available FAQs and HOWTOs to some degree, yet the good ones summarize the relevant points, make dry documentation more accessible, and give the reader some new insights. Because Bookman's Linux Clustering suffers from heinous spelling, grammar, and style errors; deals primarily with outdated software; contributes little new to the discussion; and doesn't speak to non-admins, I can only recommend that those interested in Linux clustering stick to online FAQs and HOWTOs.
You can purchase the Linux Clustering: Building and Maintaining Linux Clusters from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
Sometimes I still wake up screaming from reading that!
--------
Free your mind.
Why is it so tough to find a decent book on this topic? Even O'Reilly failed here.
Quod scripsi, scripsi.
Not to mention he knows *nothing* of relational theory:
http://www.pgro.uk7.net/qu092902.htm
Thanks,
--
Matt
How bad was it? It came with a CD-ROM that was supposed to automate the process of setting up a Beowulf cluster. None of the software on the CD-ROM worked. Running the install script printed out a message telling you to go to a Web site and download the newest beta version of the software. No such software was available ... ever. O'Reilly shortly withdrew the book ... and, reportedly at least, fired the editor who approved it for publication.
Want more details? Here you go. Waiting for this book, and then discovering slowly just how awful it was, set back a clustering project at my workplace by several months, by the way.
...the book is divided into eleven chapters, unevenly distributed among three sections...
Kudos to you, my good man.
I was going to respond to that comment with a clever, humorous comment, but I think that I need to go negotiate a book deal with New Riders.
:P
My blog
Wait, my universal translator is busted here. Is this a new rider's book or an o'reilly book? How does "highly regarded book" do "nothing to improve new rider's reputation" ? Maybe you should have discussed it with fewer beers?
In my mind, this is simple -- I have never read a worse O'Reilly book than Building Linux Clusters. There is a reason that ORA pulled this book out of print after only 6 months, and haven't even bothered to try to fix it and reprint a new edition. It was basically a commercial for the company the author ran, it read as if it hadn't been edited (spelling and grammar mistakes everywhere, included pictures were of the wrong thing that the text referred to), and the code included was so buggy it wouldn't work at all without a lot of fixing.
This was the first book on Linux Clustering I read, and I was hugely disappointed
I bought that book... any idea how to get a refund?
"Backups are for wimps. Real men upload their data to an FTP site and have everyone else mirror it." -- Linus Torvalds
Uh.. what was wrong with MySQL and msql? I mean, it wasn't the most incredibly intensely mind-opening technical book i've ever read, but it wasn't useless, either. Far as i could tell the first couple chapters introduced you to SQL pretty well (which isn't exactly difficult, but they didn't really flub it), which you would never read more than once, and the rest was just various bits of random somewhat-disorganized reference material, sample sql, and sample database code in a few languages. It wasn't really any more useful than it would have been to have a printed and bound book that just contained the mysql manual, the dbi perldoc, and the manpage for the c database library.. and now that i'm used to mysql i just use the online manual.. and i will probably never dig my copy of the book out of the bottom of my closet never again.. but i don't really think i'm -sorry- i bought it.
And of course, it's been a long time since i first read the book, but i don't remember it being unpleasant. Why all the disdain?
Irritable, left-wing and possibly humorous bumper stickers and t-shirts
His complaint was the lack of editing made it almost unreadable. I.e., re-reading a sentence several times to figure out what it said.
Good grammar and spelling aren't "windowdressing". They are essential for easy reading.
The bitter lessons of a veteran coder: http://bitterprogrammer.blogspot.com
Weird sentence constructions can make it very hard to focus on the information.
www.vanheusden.com - home of Multitail, HTTPing, CoffeeSaint, EntropyBroker, rsstail, bsod, listener, nagcon, nagi
For somebody who wants to learn about Linux clusters. I've played with Mosix and was impressed. What are good books and sources to learn about Linux Clusters?
Suncoast Linux - Sarasota, FL
I have to add that 'Apache: The Definitive Guide (Second Edition)' was pretty horrible as well. Like the MySQL book, it was heavy on re-hashing available information and light on useful information like a dash of theory or a hint of how the authors used it to solve a particular problem.
And I hate it when O'Reilly comes out with a bad book, because generally their books are great.
Why buy one prebuilt, of course....
I hate to turn this into an Ask Slashdot, but truth is I could really use a good book on Linux clustering, especially if it covers:
1. Clustering (not just replicating) MySQL databases.
2. Network attached storage.
3. Load balancing and failover.
4. Probably six other things I'm not thinking of right now.
Anyone got any suggestions?
I realize that your post was meant to be a joke, but I have to point out that spelling errors and grammar mistakes do nothing to instill confidence in the reader. It seems unlikley that any of the information in the book was verified, nor the sources checked, if no none could bother to run the text past a spell checking program.
We really need your help
http://www.gofundme.com/help-sherry
Sell it on e-bay in a few years. The rare/novelty factors should make it sell for better than what you bought it at - there's your refund plus interest.
espo
"...there's love and darkness and my sidearm" -- Moby
Said the short, bald, vegan pacifist.
I'm going to go out on a limb and say he was trying to be funny. He succeeded, in my opinion.
this is getting old and so are you
blog
MySQL book to be THAT bad. I didn't pay for it, so of course I wouldn't have felt cheated. We had a red one around for a while but I forget who put that one out. It was a little better.
From the review:
The book is divided into eleven chapters, unevenly distributed among three sections:
That's good news: I would hate to read a fractional chapter.
I want to drag this out as long as possible. Bring me my protractor.
I know mSQL had a release in Jan past.. but does anyone know the merits of using mSQL vs MySQL? We all have pounded the MySQL vs Postgres vs Uber-commercial (oracle, ms-sql, sybase) to death.
-
ping -f 255.255.255.255 # if only
Second worst is the php pocket reference. It was ridiculously out of date, no index or corssreference, pretty much just a poorly sorted listing of functions with one-sentence descriptions that didn't tell you much that couldn't be guessed from the funtion name. At least it got money to the php developers, i guess. The online documentation is better
that book is very poorly written. Beowulf Cluster Computing with Linux is a much better book.
Here are the books I've found most helpful on MySQL (and using MySQL with other things):
MySQL- Paul DuBois
MySQL and Perl for the Web- Paul DuBois
PHP & MySQL- Welling & Thompson
Thoughts on stocks, markets and trading
I think it's pretty clear that the original parent poster was pointing out the redundancy in the story text. Why was there a need to point out that the 11 chapters were unevenly distributed? It's not as if they could be evenly distributed is it? That's what the guy was saying.
"Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
Nix. Microsoft Bob is still going for $15, less than its original list price.
Shutting down free speech with violence isn't fighting fascism. It IS fascism!
There *ARE* some good New Riders books - it's just that they tend to deal with digital art:
"Digital Texturing and Painting"
"Digital Lighting & Rendering"
New Rider's focus is more on the artist / animator / illustrator side of things - and at that they excel (the above two are those I'm most familar with, and they are excellent).
I'm sure they'll gradually improve their hardcore technical books, but it's stupid to dismiss "all" their books as being bad. Just like O'Reilly has a reputation in some circles for being overly dry and out of date - *some* people find their books useful.
O'Reilly's Linux Hacks has one of the best explanations I've seen for setting up mysql replication. Load balancing and failover area are topics in their own right, but the Linux High Availability HOWTO is a good place to start. In general, the ibiblio site has been a helpful source.
http://tinyurl.com/4ny52
Actually, it would be nice to slow down the pounceposters who stab us with one-liners as soon as an article hits the front page in order to grab that funny karma goodness...
So long, michael. Don't let the door hit you...
In attempting to point out that the original poster didn't get it, the replies have proven that they don't. He was saying that the word "uneven" is unnecessary, because 11 chapters can't possibly be divided into 3 sections evenly. Omit needless words! That's why it was funny. Sheesh.
Do you "get it" now, or do we need to lock you in a room with RMS?
WMBC freeform/independent online radio.
Waited a while, didn't you? That book was withdrawn from sale two years ago. People who wrote to O'Reilly customer service at the time did get free books (an up-to-date copy of Linux in a Nutshell in my case, twice as thick and more useful for clubbing lusers^W^Winforming coworkers with) ... but I don't know if they'd do anything for it now.
the book had two "technical reviewers" but their contributions seemingly didn't include fixing mangled syntax and strained style.
When you see a book in print, don't assume that the suggestions of the technical editors/reviewers have been heeded. The author basically has final say over the content of the book -- meaning that a tech reviewer/editor can be completely ignored no matter how much they complain about the content of the book or how much it doesn't address what it should.
And, the tech reviewers/editors are explicitly asked not to try to fix grammar and so forth -- that's supposed to be the job of a different editor.
Also... I'm surprised to see a review of this book popping up now, it was published about a year ago.
Funny that the reviews of the book look like this
So much for trusting reviews.........
.ACMD setaloiv siht gnidaeR
You didn't have to know anything about the book to post what you did. The summary on the front-page was all you needed. +4 Funny??
Let me be the first to thank a work colleague for jumping to my defence. Let me also be the first one to call him a complete idiot for not checking just who exactly was logged in at the PC he posted from.
Oh well, I guess he's going to be buying the first round of drinks on Friday evening then.
"Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
The newer edition, Managing and Using MySQL goes a long way to correcting the sins of the first book. I haven't read these others to compare directly, but I find the new edition a lot more clear and useful than its precursor.
7 November 2006: The day Americans realized corruption and incompetence weren't addressing 11 September 2001
From the review: (but ignorance is no excuse for a UNIX systems administrator)
That's right. Also,
Ignorance is no excuse for the law.
-- -- Warning. Do not stare directly at the sun.
Er, I'll still have it, I still use it. I didn't think it was a terrible book, although I've always known it wasn't brilliant. Still, I've ended up using it actually quite a bit. The new book is better, no question. But if you have to lay the two side-by-side, well, that just means the first one isn't *that* bad. It would be nice if there was an authoritative resource for computer book reviews, some place the really tried to give the low-down and had a dependable, objective reputation ...
Chr0m0Dr0m!C
It seems that a large majority of MySQL users also know little or nothing about relational theory.
Of course. If they did, they wouldn't be using MySQL.
Having the occasional less-than-glowing review on slashdot can be refreshing change of pace. But I feel that they are unnecessary. Letting these books lie in fallow obscurity is perhaps a better strategy especially when there are so many other books that need publicity. One problem with reviews of technical books is that they depend on the technical proficiency of the reviewer. What may seem bland and uninteresting to this reviewer may seem interesting to someone totally unfamiliar with the topic or someone who just wants it as a dead-tree reference guide.
BTW, I don't see anything wrong with regurgitating man pages and how to's in book form, especially if explicitly states. Mark Sobell's practical guide to rh linux 8.0 is a perfect example. This book includes man pages/how to's while including better examples.
Finally, if the reviewer didn't like this book, why didn't he recommend a title or two that did cover this topic well?
(PS, I do occasional book reviews for slashdot myself.)
Robert Nagle, Idiotprogrammer, Houston
Imagine a Beowulf clust-- oh wait.
I saw the title for this review and was happy. Just this morning I was talking to my director about clustering, something I've wanted to toy with for some time so I was hoping for a good review. As has been pointed out, good books on clustering are hard, if not impossible to find. Oh well, back to the howto's for me.
/. . Anyway, he apparently read something in Scientific American recently about clustering and wanted to apply it to an auditing project that we're working on. Not a cluster but some of the underlying theory gave him an idea of dealing with all of the varibles we have.
On the funny side, my director started the conversation with "have you ever heard of a Beowulf Cluster"? He didn't understand why I couldn't stop laughing. I obviously spend waaaaaay to much time on
I wouldn't say I'm a bad gambler but the last time I went to Vegas I even lost a buck on the soda machine.
No the worst book was the Debian book. http://safari.oreilly.com/?XmlId=1-56592-705-2 I also hated the cluster book but trust me the Debian was worse.
Cypherpunks: Civil Liberty Through Complex Mathematics. Those who live by the sword die by the arrow.
The topic reads: "O'Reilly's worst dud: MySQL & mSQL"
/. archive. What was so bad about this book?
MySQL&mSQL was my first O'Reilly book, back in my old days in school. I spend many nights reading it and many classes trying out the things I read.
I still like it although it has become completely outdated now (at least my edition).
Maybe I should have a look at the
Are there really any truly fault tolerant clusters available for Linux and MySQL? I mean like to have a set of two, three or more identical machines networked together such that the databases on all are kept in perfect sync with one another and a client workstation app connecting to that database which runs on the group, not necessarily exactly to one server machine, will automatically and seemlessly and invisibly to the end user switch over to another if one server machine quits. For example let's say I have a taxicab dispatch center in a city with a dozen workstations for the dispatchers who take calls from customers and enter them into the system to dispatch the next available nearest taxi. Suppose that Crazy Larry, the drunk psycho mechanic wanders in from the back shop into the front office's computer room and sledgehammers the main database server in a fit of rage. I need all the dispatchers workstations to automatically switch over to the backup server(s) without missing a lick, or the dispatchers even knowing anything happened to the system.
Is there any clustering technology available for Linux right now that will accomplish this? I know that if the servers were IBM RS/6000 machines arranged in a AIX/HACMP cluster and running Oracle 9i, this scanario is very do-able (provided that we eliminate SCO from the picture).
Insightful.
I thought it was pretty obvious that those reviewers never actually attempted to do anything with the book, or particularly the CD-ROM; they just browsed the former and never let the latter touch their Windows systems. From a cursory (read: sloppy and shallow) first impression it is not nearly as bad as it is on a closer look, and a trade-rag pseudojournalist with enough cocaine in his system would probably find it quite impressive.
That's why I don't buy many books anymore. I can get most of the relevant information for any current topic/projects from the internet. I think the most innovative thing created in the last few years was tabbed browsing, I love Galeon.
Can I barrow it?
--==-- I've found Karma to be a relative thing... Ya know, the kind you invite to Christmas...
Sheesh, Buddy, it's in the FAQ.
Their PostgreSQL book is incomparably worse. The first edition is essentially useless.
"The book is divided into eleven chapters, unevenly distributed among three sections"
so why is this a bad thing?
At the least, they can keep me from spending my hard-earned cash on poor products.
However, I do agree that it should be a requirement that if you leave a negative review, you should also show an alternative title.
Q) What do you call the computer lab of a group of open source monks?
---
A) A linux cloister.
chaos-five
Please, oh! To concentrate on weird sentence structures hard make it? On facts concetrate not structure. Enlightened you will then be.
Andrew King's book Speed Up Your Site is the most enlightening book I've read in a year; well organised, well structured, readable, teeming with useful information, and it's published by New Riders. Eric Meyer on CSS, also New Riders, comes a close second. Rule of thumb, there's dog food in any stable.
the june issue is entirely clustering.
it's pretty funny that a reviewer who trashes a book for its grammar employs faulty grammar himself...
REPORT ALL OBSCENE MESSAGES TO YOUR POTSMASTER
I didn't know the older edition was bad... I have the newer one though, and I concur - it is pretty good.
Jeremy
So I read online, whatever I found that was up to date and settled on the satisfying OpenMosix and... it works ! :-)
Non-Linux Penguins ?
If you only want to have some servers giving redundant services, like web or mail, this is quite straightforward to configure and use.
Pen, a load balancer for "simple" tcp based protocols such as http or smtp. It allows several servers to appear as one to the outside and automatically detects servers that are down and distributes clients among the available servers. This gives high availability and scalable performance.
Ok, this book is bad but image a Beowulf cluster of those!
What I learned:
1. don't mention Beowulf again, even in irony
2. don't feed the trolls
3. don't mention moderation
4. don't comment on anticipated future negative comments
5. don't annoy
6. Last and most important: don't detract from the story or conversation
It was unintentional and I wasn't looking for replies, but I can see I made quite a number of mistakes in one post. It was a first and a last post of its nature from me. Not to be repeated.
Esteem isn't a zero sum game
They must have pretty good editors, because they do avoid the mistakes most computer publishers make, like sloppy revisions that leaves Windows 95 material in a book on Windows NT. And they seem to have put a lot of work into their publication workflow. But it's pretty obvious that nobody at O'Reilly is in a position to tell the author to watch the stream-of-consciousness prose or question the relevence of his material.
This is becoming very common in the tech book industry. All the tech book publishers are trying to foist all kinds of reall bad crap on us. Northcut's "Network Intrusion Detection" and the Solaris 9 exam cram book I started reading (and quickly dropped ... don't remember the author, some Prof.) both suffer from the same sort of issues.
... I would be embarrassed(sp) to be one of those technical reviewers.
... wow, what an unbelievable piece of crap! But heck, the people producing this stuff aren't dumb ... they rest on their laurels while we keep buying their trash!
Terrible writing style, bad use of language (not that mine is great, but I am not writing books), spelling mistakes, blatantly wrong information, "Technical Reviewers" who must be sleeping at the wheel
Not that this is a tech book industry issue. My wife rented "Atlantis 2" for my daughter
Mark
Ancient Budo Master once told me: "All your bruises are belong to us."