Slashdot Mirror
Linux Server Hacks
About the book LSH is not just about the Linux operating system, per se. Despite the title, it spends more time covering applications which can run on Linux than it does the Linux operating system itself. It is composed of 100 "hacks" all grouped together into like areas, such as "Monitoring" and "Networking". The style sort of reminded me of O'Reilly's Cookbook series, and I find it to be an easy format to read. Indeed, if the book was larger, it could have easily been called "The Linux Server Cookbook."
After a somewhat cheesy forward by ESR and a recognizably standard O'Reilly preface, LSH starts out the hacking with a section called "Server Basics," and it's here that most of the Linux-specific tips are. You get to learn how to pass args to LILO, stroll through /proc, tweak the Linux kernel, play with hdparm and so forth. This chapter left me thinking that this was all stuff every admin should know, and not much of it was new to me (if you've used Linux for more than a couple years you probably won't find much here that you haven't at least heard about before). If you are new to Linux however, then this chapter will be valuable even if you stop reading the book right at chapter two.
If the book had to be divided into two parts, the first chapter would be titled "Part 1: Linux the OS." The balance of the book would then be called "Part 2: Linux Applications." Subsequent chapters each tackle one area of services or applications that run on Linux, such as CVS or rsync or ssh, and it's very easy to find something interesting purely by looking through the table of contents. The book's grouping of hacks into like topics helps, I think, because you can easily pick out what you want to see more of without having to wade through that which you don't find terribly interesting. For example, if you only deal with your personal Linux workstation, then you can easily disregard the "Information Servers" chapter without missing other valuable content. I personally found the "Networking" and "Monitoring" chapters to be the most useful. The "Backups" chapter was interesting, the "Scripting" chapter not so much. Each chapter starts with a summary of what's to come, so if the table of contents isn't enough to find the good bits, then just reading those summaries can give you an idea of whether you'll find anything useful to you.
The book includes a fairly complete index, but I didn't use it very much. I found the table of contents, with its list of each hack's title, to be useful enough. I suspect that when I pick the book up a couple months from now looking for something I had read about I'll get more use out of the index.
What's to likeAs I mentioned above, the book is very easy to read. Flickenger has a "conversational" writing style I found easy to parse. If you hang out with Linux geeks very much, you'll recognize his way of communicating and easily assimilate what he has to say. His advice is sound, his skill level high (the same can be said for the other contributors as well). The book's layout and organization made it easy to find specifics and will ensure that it gets used as a reference later on.
You might be wondering about the code samples in this book: there are a lot of them. I didn't check, but I think each hack had at least one CLI listing or bit of example code. This made the book much more valuable than if it simply told you want to do; "seeing" the hack in action helped tremendously. In fact, I'd have felt disappointed if Flickenger hadn't included as many examples as he did. Most of the code is Perl, with some shell mixed in. The example code is well written and properly placed, so if you don't know Perl or shell you'll still be able to make use of the hack.
Each hack can stand on its own. This makes the book easy to read, and ensures its place as a reference. I didn't read the book sequentially at first, but I went through the whole thing regardless. Some hacks refer to other hacks, and I found myself reading the book as if it was hypertext, as is mentioned in the preface. Again, this also means less time spent reading that which you already know (or find boring) and more time spent thinking about something more useful.
The book is distribution-agnostic. I couldn't find anything that would upset a Debian user or would flummox a Mandrake fan. While this might have more to do with the bulk of the hacks being on the application level, I found the lack of an axe to grind refreshing nonetheless.
The book doesn't assume l33t-ness nor coddle the reader. It assumes you know your stuff and are a professional, and in doing so finds its voice rather well. This gave me a sense of admiration for the author and allowed me to absorb the knowledge being imparted with ease.
Although not specifically about the book, O'Reilly has set up a website devoted to their "Hacks" series of books. Users can send in their own hacks, which helps flesh out the content in the print edition.
What could be betterESR's forward, titled "How to Become a Hacker," was just silly. The forward added nothing to the book, and I find the whole "zen of hacking" schtick tiresome after only a short while. Yes, "hack" is a cool word, but one which easily suffers from overuse: it suffers a lot in ESR's forward. The forward also contains a plug for ESR's book, which I thought was somewhat tacky.
LILO is referred to in several places, but there is not a single mention of GRUB. Where the boot loader was being discussed, an "If you use GRUB, you'd want to do it this way..." aside would have been welcome.
The "Information Servers" chapter is very large, but only deals with BIND 9, Apache and MySQL. If you don't work with any of these three, then fully one quarter of the book will be useless to you. I would have really liked to see mail servers (especially Postfix and Qmail) mentioned, and including tweaks for an ftp daemon would have made the book that much more valuable. I would have also liked to see sshd covered; the book contains only ssh client hacks. Finally, a hack or three about PostgreSQL would have been nice.
The "Scripting" chapter could have been replaced with a "Security" chapter. There are only 4 scripting hacks, and they aren't all that useful. Although the book has a security-conscious mindset running throughout it, I felt the lack of a section devoted specifically to security was a glaring omission. In fact, I almost didn't buy the book when I noticed that the table of contents didn't list a security chapter. It was only after reading a hack or two that I could see security was going to be mentioned.
Another area I expected to see was one with hacks involving package management. A whole chapter dealing with this topic would have certainly been welcome to users of Red Hat, SuSE, et al. I suspect that such a chapter might have broken an unwritten editorial rule about remaining distribution neutral, however. And Debian users would have found anything beyond an apt-get one-liner superfluous, so I can forgive the "omission."
Although the title of the book is "Linux Server Hacks," someone using Linux as a workstation would also find the book helpful. For example, Flickenger includes two hacks on burning CDs, a hack on displaying the load average in the title bar of an xterm window, and so on. I got the impression that the server-centric focus wandered into desktop land quite a bit. Because of this, I thought that some hacks involving window managers should have been included. I've tweaked vnc to run blackbox on more than one occasion and expected to see things like that mentioned. This is a niggling complaint, however.
I found myself wishing the book was longer. At US$24.95 the price was right, but I would have rather paid US$34.95 for 150 total hacks.
Finally, the book looked somewhat rushed. There were more than a couple formatting errors (typeset characters visible, etc) sprinkled throughout, and all the code examples were unindented; it was as if all the tabs were stripped out by the printer. While the lack of indenting might confuse those who don't know Perl or shell, the only "real" consequence of this is that the lack of tabs in the makefile examples on pages 27 and 28 prevent them from working.
SummaryBased on this review, it might seem that the bad outweighs the good where Linux Server hacks is concerned. I don't think this is the case, and I would caution anyone against taking that view (rather, I'd have them glance through the book at the bookstore before deciding not to buy it). I think it should be noted that given the usually high quality of O'Reilly titles, it's far easier to spot what could be better than what is likeable. Like the old saying goes, nobody notices a clean kitchen unless it isn't.
None of the "bad" things would keep me from recommending this book, and I found Linux Server Hacks to be a very useful -- both as a future reference and as "thumb through while waiting for the train" sort of read. There's not much in it which is "new", and most of the hacks would border on common sense for the seasoned sysadmin (although I'd be willing to be that even the most grizzled admin would find something new or interesting). Indeed, nearly all the information in the book can probably be found on the web somewhere. It is nice, however, to have everything collected in one place and organized into specific groups. Linux Server Hacks would make a good addition to the bookshelf of anyone, regardless of their skill level, who finds themself administering a Linux machine, be it a server or workstation.
Table of contents- How to Become a Hacker
- Preface
- Server Basics
- Revision Control
- Backups
- Networking
- Monitoring
- SSH
- Scripting
- Information Servers
You can purchase Linux Server Hacks from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
It is also not a book which will teach you how to break into Linux servers.
Then what good is it!?
why cant all this information be on a searchable website? and charge me subscription...
Consensus is good, but informed dictatorship is better
Does this book have any methods for filtering pr0n from user mail accounts, and indexing/organizing it correctly for the administer to 'review' and archive? I know this admin would surely welcome suggestions that would help me better utilize my time in this most important area.
The book will probably not make you a better admin, but it will almost certainly save you some time
More time for recreation makes me a better admin. More time for automation and documentation makes me a better admin. And, of course, more time for Slashdot makes me a better admin.
UNIX Papers
for UNIX Developers and Power Users
ISBN 0-672-22578-6
Like I said, it is old, but sed, awk and C haven't changed over the years. This has some great information on shell scripting, NFS, and email.
Click here or here.
I had a few extra book places so I checked this book out last week. I was suprised how useful much of it was. I have been working with linux for years and there where plenty of things I had never done before, but would have had I known of them before. I may even get a copy for everyone at the office.
Since they don't work out of the box like Microsoft products, you gotta buy a fucking book to kludge them together before you can use them.
Yea, everyone knows that Windows users are the KeWl3sT anyway, right?
Idiots like you are just as bad as the Windows bashers. I use both. I like both. Both piss me off in some ways, delight me in others. Anyone who can't see value in both are just blind or stupid. Now go crawl back under your rock and die a miserable death.
Punk.
I agree that the ESR forward should have been deleted. However, this book is a nifty collection of various hacks that probably would take you forever to stumble upon if they weren't in this book. (You're probably too busy administering or programming to experiment all day long).
/etc/* files that have lines commented out, no explanation why. Having a revision history clean the clutter, makes a backup, and lets you know why and when something was changed.
Using RCS/CVS to track revisions to settings files is just an example. I've seen far too many
That's the sort of time saving, "ehy didn't i think of that" tips you'll find.
First book I've read that treats you like an experienced System Administrator. Not for the faint of heart or inexperienced. I really enjoyed it!
To some of you Uber network admins out there this book won't be very helpful. But to me, someone whose been net-admin'ing it for 2 years this was very helpful! Shows you lots of nice tricks. I found the section on utilizing ssh to its full potential extremely useful! I never thought of doing backups over ssh before! I'd rate this book 5 out of 5 stars personally!
LFS. Have you built your system today?
-- Power corrupts, but PowerPoint corrupts absolutely.
www.tldp.net
There's was a book review of this same book about a week or two ago, wasn't there? I bought the book and have been pleased overall with it, but there wasn't really anything new or exciting, just a few tips and tricks. Note you can find most of these by going to www.google.com/linux and looking up tips and tricks. One example would be that you can find out who is hogging the most disk space using an alias for du, like this:
du -cks | sort -rn | head -n 10
Pretty simple, yet really effective. This book is full of little things like this.
Everyone is entitled to their own opinion. It's just that yours is stupid.
ESR wrote a foreword. Forward is a direction, foreward is piece of writing at the front of a book.
Canthros
For Pete's sake: It's "foreword" (ie. fore-word). Defined as "A word said before something else; hence, an introduction, a preface." (OED).
Why the heck would it be called 'forward'? Do people who make this mistake think it is the suggested reading direction?
As I mentioned above, the book is very easy to read. Flickenger has a "conversational" writing style I found easy to parse. If you hang out with Linux geeks very much, you'll recognize his way of communicating and easily assimilate what he has to say.
:-)
You know that if you start using words such as 'parse' in every day language, you probably do hangout with geeks very much!
(and they probably find words such as parse easy to communicate with, too)
what about all those "Windows Secrets" and "make Windows Faster" books out there? As someone already posted, it's all about optimization.
Perhaps you're not getting as much from a Windows OS package as a Linux Boxed set. For a fraction of what Windows costs, you can get RedHat (or any other distro) that comes with the OS, lots of software, and a big manual that explains a lot of things. Windows..all you get is the OS CD(s) and a booklet
$cat
Like there aren't books for Windows folks for tricks you can pull to make your life easier on a Windows box? Aren't there are a bunch of classes available for MCSE types?
Yeah, you might want the book if you had not already thought of some of these tricks. That is the point of reading and learning, duh!
Give me a break. Every admin knows there are little things that can be automated and worked from a base install to help them get through the day and get their stuff done no matter what OS you admin.
I propose this to the community. What is the neatest hack/trick that saves time from your day in terms of programming or system administration?
BTW, any tricks I don't care if they are straight commercial Unix, Linux or Windows.
ACK
Those who love UNIX (and UNIX-inspired operating systems) will surely adore Linux Server Hacks by Rob Flickenger. For decades, a mysterious sect of bearded wizards has dominated the inner sanctums of our network infrastructures, inspiring the awe of onlookers by crafting clever scripts and piping output in ingenious ways most of us never even thought of. This small but marvelous book attempts to steer apprentice wizards in the noble direction of clever system administration, with examples taken from experience in O'Reilly's own LAMP networks.
The book begins with a refreshing introduction (by esr) detailing what it means to be a hacker. No, not the hax0ring w4r3z d00dz of frequent media attention, but the aforementioned bearded variety who spend most of their waking effort forging uncommon techniques for solving otherwise dull problems. Kudos to Mr. Flickenger (and O'Reilly) for not only acknowledging the difference, but celebrating it.
As the title would indicate, the audience of this book is the administrator in charge of a server--that is, a Linux box performing only a couple of dedicated tasks, probably of a network-oriented nature. Although Linux enthusiasts from the desktop realm are not part of the intended audience, they will almost certainly pick up a thing or two from the material anyway.
The book is organized into the following sections:
I think the real magic of this chapter isn't necessarily the tips themselves, but the creative process behind them; the author is demonstrating a methodology for dealing with common problems by introducing clever solutions. This will ideally inspire the reader to deal with other problems in the same creative manner.
While we are on the topic of linux books, I was wandering if anyone would recommend a linux book for a beginner (but someone who recompiled the kernel and messed with X before even knowing the 'less' command :-) ) Your help is appreciated.
Free speech is getting expensive...
Yeah, I agree. Linux is great - I've loved it when I've had access to it, although I can't say that much right now - but I don't mind using Windows. Honestly, if I had the choice, there are few things I'd change about Windows as it is now - it's crashed to the point that I need to restart the system maybe four times in a year, and application specific crashes are fairly infrequent. I'd still rather be using Linux right now if I had the opportunity, but this isn't my computer... but yeah. They both have advantages and disadvantages, people need to realize that.
That sentance does not make any sense. If it saves you time, then wouldn't you be a better admin?
I don't know if the computers can sort out the good pr0n you want to see, but I imagine they could with the right filters sort them by breast size, hair color, and number of people involved. Even this small bit might really help you utilize your time in "this most important area" much more effectively.
I only look human.
My mother is a halfling and my dad is an ogre, so that makes me an Ogreling
...that make you go ooh thats clever. I've always found the difference to be between a good sysadmin and a great sysadmin is when they do something and you go wow now thats smart. Some one like this
Rus
Cheap UK and US VPS
Bravo,
That reply warrants a fan designation!
I stand corrected.
-- Hey, what the hell, it's only slashdot..
I appreciate the correction. If I find myself in a similar situation (taking pot shots at slashdot poster's grammar and spelling) I'll remember that aught means all/anything/everything, and ought means obligation...
:)
Or, moreover, that I should probably get my flames peer-reviewed before I spout them out!
-- Hey, what the hell, it's only slashdot..
How was the word abused? A pejorative, as you know, is "a disparaging or belittling word or expression". It always seemed to me that "hack" is used to describe criminals and script kiddies, which is exactly the opposite connotation the foreward would have you believe. I've also seen it used to describe "hacks" which were shoddy pieces of work and in no way clever.
However, there is much that is stylistically wrong.
Seems I got my point across, in spite of not having proofread it before submission.
Were I reading a text on any non-geeky subject I would be very surprised to see those particular phrases, as the immediate impression is that the author picked a set of words from random points in the review and then checked for alternatives in a thesaurus. This is the expected behaviour of a smart-ass 14 year old, but is not "exquisite English".
Nope. I'm well beyond 14, although I'd much rather be called a smart-ass than a dumb-ass. I wrote the review last night in one sitting, and not a single thesarus was harmed in its making. I didn't use any word or phrase I don't normally use, so pardon the perceived affectation.
-B
Ash and Hickory, straight-grained and true, make excellent bludgeons, dandy for the cudgeling of vegetarians.
The book doesn't assume l33t-ness nor coddle the reader.
I hate to sound 'l33t' but I wish there were more books for people who has used linux for a long time. It's hard to aquire any new knowledge when most books are targeted at people with little experience.
Of course there is a lot of good places on internet to get good tips and advice but that defeats the whole point of a book.
This provides a segway into using CVS for controlling revision of large software projects.
...sounds like a good way to interview your prospective new server-master. Give them a blank server box and a play domain. He gets to set it up however. Have him coder 'er up to what he thinks is "good stuff", serve wise and security-wise. Have a nice strange web page fulla blinkenlights graphics and flash and whatevers, THEN see if you can get it posted as a story on slashdot. Server don't cut it,or gets owned real quick, he don't get the job. Forget all the other resume stuff.
Who said a person made this mistake? How do you know it was not the auto-correct feature of M$ Word? Be glad the M$ meat heads don't give books foreskins instead.
Foreskin - a protective collection of words at the start of a book. Some people think of them as superflous, others call them Introductions.
How's that for forward of me?
Ever heard of a book so up front?
The direction depends on it's state.
OK, I'm going to stop mow, my wife is punching me.
DMCA, Hollings, Palladium. What might have sounded like paranoia is now common sense.
My personal favourite is the Linux Gazette, but there are others (too lazy to reahch for bookmarks now ;). Don't overlook past issues even if they are pretty old, because some of the tricks discussed haven't changed much over the years (like motd, rdev, tcsh etc.), but of course some of it is to be viewed from a historical point of view =)
I haven't seen any MS OS that will work at all during first boot - they all take a minumum of 3 or 4 boots before you get to the stage of a working OS...
On the other hand, I added yesterday "Unix Power Tools", to my safari bookshelf and this one really absolutly rocks ! Not quite like a cookbook, it's more like a guide to get the most of Unix. Even on very basic subjects, and even if each topic is generally concise, I found alot of things I had never heard of. And i'm really learning alot about using the shell itself. I realized there are a lot more nice features to help edition the combination of emacs bindings and C-r. The authors not just tell you "this feature do that", but demonstrate how they use it all the time in their day to day job. There are alot of things that I thought were useless for me but it all makes sense while reading this book. And I've not really looked into the others chapters yet, but they look as good as this one.
In fact those books aren't even comparable : one will be read in one day and after having noted the things you'll find inside it'll sleep on your shelf. The other one will give you an insight each time you open it, and you'll open it often.
h
testing out my trending skills
You know that one can use a pejorative, right? Something can be called a pejorative? That it can be a noun as well as an adjective? There's more than one definition for the word?
Shit, why am I bothering to respond to thick-headed ACs...
-B
Ash and Hickory, straight-grained and true, make excellent bludgeons, dandy for the cudgeling of vegetarians.
I remember coming across the hacker-howto years ago, when I was a windows-only newbie, and it actually inspired me to start to learn to program, and figure things out. That's what it was intended for; not for a server hack intro. Hence, that's probably why it seemed so out-of-place.
philcrissman.com.
Hi - Wee's wife Tess here. I just wanted to note for the edification of the vocabulary police that Wee does, in fact, employ multisyllabic words both in speech and in writing on a regular basis and entirely without pretense. It's one of the things that I liked best about him when we first met. Literate guys are hot!! ;-)