Please create an account to participate in the Slashdot moderation system

 


Forgot your password?
Close
typodupeerror
×
Unix Books Media Operating Systems Software Book Reviews

The UNIX Systems Administration Handbook 86

Posted by timothy from the weighty-tome dept.
Mike Knell contributed this review of what is perhaps the most definitive collection of Unix practice and wisdom. It's even been newly updated to reflect the widespread influence of the other*NIXes. In fact, just look at the names of those who contributed forwards to this edition, and you'll see how it ties together the old and new continents of the Unix world.

UNIX System Administration Handbook
author Evi Nemeth, Garth Snyder, Scott Seebass, Trent R. Hein, et al.
pages 850
publisher Prentice Hall
rating 9/10
reviewer Mike Knell
ISBN 0130206016
summary The updated third edition of one of the Holy Books Of UNIX.

*

Introduction

There are a few books which most sysadmins will mention in hushed tones when discussing reading material, and one of those is the famous "Red Book", the second edition of this book (the new edition's purple). I'd heard good things about it ever since people actually started paying me to do systems admin rather than just mucking about with computers for fun, so when the new third edition came along, I was keen to take a look at it.

The book aims to cover the basics in a wide range of areas that good UNIX admins need to know about. The contents range right through from booting the system and adding disks to dealing with users and the inevitable people-politics that help make the job so . . . varied and exciting. While the second edition covered six commercial versions of UNIX, the new edition has simplified this and now covers two commercial UNIX systems (Solaris 2.7 and HP/UX 11.00) and two free operating systems (Red Hat Linux 6.2 and FreeBSD 3.4), which accurately reflects the changes in the UNIX world since 1995. The last edition also came with a CD full of useful tools, but there's no such companion to the new edition -- near-universal Internet access for sysadmins has made such things far less useful than they used to be.

What's Bad?

The big shock upon getting hold of a copy of this book is the price tag. Here in Ireland, it's going for about IR£68 in shops, and the U.S. list price is $68. This is a lot to pay for a book, and to my mind it's quite likely to put off a number of potential readers. I can understand the price tag -- with four principal authors and 850 pages of dense information it's bound to be costly, but it's a shame that it had to be quite so expensive. Online it's available for about US$55, but that's still not cheap.

It should also be made clear right from the start that this is not a book for newcomers to UNIX. Don't look here if you're wondering how to list files or send mail -- there are plenty of books out there already that cover those areas more than adequately. The book assumes that the reader is already familiar with UNIX from a user's point of view.

What's Good?

When you get down to actually reading the book, though, it's immediately apparent that the authors really know their stuff. It's a book written from the perspective of people who know what it's like to be a sysadmin in the trenches. They have opinions that are obviously derived from painful experience, and aren't nervous about sharing them when the need arises -- if they think something sucks, they make damn sure you know about it. The information density is remarkably high for such a fat book, and the writing has a light touch which makes it extremely readable both as a desk reference and as bedtime reading. The advice given is sensible and solid, and I found myself nodding in agreement with the authors at some points, while feeling somewhat chastised and guilty at other points for not having done some of the things suggested. The humour helps to keep the book readable rather than getting in the way as it could easily have done.

As with all good computer books, there are cartoons (drawn crudely but funnily by Tyler Curtain) scattered through the book. My favourite is on the subject of "Co-operating With Windows." It involves, well, brides, rednecks and shotguns, something with which anyone who's ever gone through the pain of trying to make Windows machines play nicely in a UNIX environment will identify.

Things that only need a short chapter to cover the essentials (Web serving, for instance) aren't bogged down with extraneous detail, while the areas that always inspire fear among sysadmins (print services, DNS, mail ... ) are covered in all the necessary depth. Each chapter ends with a section of pointers to further information for those needing to know more than is covered in the book. The information is of high quality and feels very reliable, making it a good guidebook for those trying to find their way through the world of confusion, vendor-specific idiosyncrasies and divided loyalties that is UNIX administration.

So What's In It For Me?

If you're just interested in the basics of how to keep your Linux system running smoothly, you'd probably be better served by O'Reilly's "Running Linux" or any of the myriad similiar works out there. On the other hand, if you're starting out in system administration, or if you're an experienced sysadmin with anything less than universal guru status, this is a splendid book. The price is high, but if you're really serious about your work it's definitely money well spent -- think of it as an investment in your career.

Besides, with forewords from Linus Torvalds, Eric Allman, Marshall Kirk McKusick and Dennis Ritchie, who am I to argue? The only reason I've given it nine instead of ten out of ten is the price. To summarise -- I wish I'd read this book five years ago.

Table of Contents

  1. Where To Start
  2. Booting And Shutting Down
  3. Rootly Powers
  4. Controlling Processes
  5. The Filesystem
  6. Adding New Users
  7. Serial Devices
  8. Adding A Disk
  9. Periodic Processes
  10. Backups
  11. Syslog And Log Files
  12. Drivers And The Kernel
  13. TCP/IP Networking
  14. Routing
  15. Network Hardware
  16. The Domain Name System
  17. The Network File System
  18. Sharing System Files
  19. Electronic Mail
  20. Networking Management And Debugging
  21. Security
  22. Web Hosting And Internet Servers
  23. Printing
  24. Maintenance And Environment
  25. Performance Analysis
  26. Cooperating With Windows
  27. Policy And Politics
  28. Daemons
  29. Colophon
  30. Index

Purchase this book at ThinkGeek.
This discussion has been archived. No new comments can be posted.

The UNIX Systems Administrator's Handbook More

The UNIX Systems Administrator's Handbook

Comments Filter:

  • Re:WOW (Score:1)

    by pigeon ( 909 )
    I wonder, how does the reviewed book compare to "essential unix system administration" by Frisch/O'Reilly? I found the O'Reilly book rather good.

  • Re:WOW (Score:1)

    by Draco ( 1804 )
    I can't believe they changed the color!

    The red book is actualy the second edition.

    I still have an old crusty copy of the first edition, aptly known as the yellow book.

    It'd be kinda silly for them to go from the yellow book to the red book to the red book.

  • Re:WOW (Score:1)

    by Gus ( 2568 )
    Since the color was also changed for the second edition, another color change should be no surprise. I like to think that this was intentional on the part of the author so that a beleagured sysadmin can reach for the book by color and get the most current edition easily.

  • It was so rife with factual errors about Solaris that I had to recommend against reading the book.

    For instance...?

    Not that I doubt you. I'm just curious.

  • I wrote this review. There's either some weird synchronicity thing going on or Mr Michaels has, ah, "borrowed" my words.
  • > DOS RULES FOREVER!!!!

    Note.. Dos.. not Windows.. Dos.. the command line operating system Windows runs on top of...

    Fight it all you like... users want the command line.... Dos and Unix.. Not Windows...
  • It excerises the file I/O buffering and context switching services of the kernel.
  • So you didn't see the first line of the article?
  • Actually, I meant this section, which is at the beginning of the actual review:
    author Evi Nemeth, Garth Snyder, Scott Seebass, Trent R. Hein, et al.

    publisher Prentice Hall
    ISBN 0130206016
    pages 850
    rating 9/10
    summary The updated third edition of one of the Holy Books Of UNIX.
    reviewer Mike Knell
  • you are my hero
  • Umm...

    1) Slashdot book reviews almost always contain a link to purchase a book.

    2) The reviews are also generally written by people who are not Slashdot employees.

    3) The general response in the comments so far also show a large amount of support for this book.

  • Why does that list remind me of the only good scene in the otherwise godawful film "Hackers"?
  • Even if you aren't in to *nix enough to justify the price...there are many other uses!

    1. Who needs a club when you've got this 850 page baby!
    2. Forget using the phone book to "boost," this will put some real knowledge "behind" you.
    3. Not up on all the tech talk? Go through the book and look up any words you don't know. Great vocabulary builder!
    4. Forget bedtime stories, this book should be able to put any kid to sleep (but watch out! you might end up with another Linus on your hands!)

    Just a friendly reminder!

  • Re:Wow (Score:1)

    by kps ( 43692 )

    Trick question. Unix mv doesn't have a -v option; that's another embrace-and-extend gnuisance.

  • Read the blue book, wake up in bed believing anything you want.

    Read the red book, and your life will never be the same.

    -Morpheus
  • We've got that book in the office, and among some of us, it's coveted. One thing I really liked about it is its chapters on some of the tools like sed and awk -- very good examples that couldn't be replaced with eighty pages of typical technical docs. The only book I've seen with such good examples is Unix in a Nutshell -- another fine book.

  • I did consider buying this book based on this review, until I saw the "Purchase this book at ThinkGeek" link on the bottom.

    Makes you wonder how objective this review is ....

  • Except they don't mention The Dragon Book here as sysadmins don't need to know about compiler design, all bow down to Aho, god of compiler design.
  • the new edition has simplified this and now covers two commercial UNIX systems (Solaris 2.7 and HP/UX 11.00) and two free operating systems

    Red hat is a 400 million dollar company. That doesn't sound like a non-commerical entity to me. There's continual misunderstanding within and without Open Source community that being open or closed source is equivalent to being commercial or non-commercial. They have nothing to do with each other, whatsoever.

    Some examples
    Open Source, Commercial: Red Hat Linux
    Open Source, Non-Commercial: Tomsrtbt [toms.net]
    Closed Source, Commercial: Windows 2000
    Closed Source, Non-Commercial: PowerArchiver [pawerarchiver.com]

    ----
  • The OS is commercial. It generates revenue via support costs, OEM deals, Red Hat Ready RHCE, and more. It just doesn't use licensing. Learn to think. Have a nice day.
  • commercial (k-mûrshl)
    adj. Abbr. com., coml., cml.

    * Of or relating to commerce: a commercial loan; a commercial attaché.
    * Engaged in commerce: a commercial trucker. Involved in work that is intended for the mass market: a commercial artist.Of, relating to, or being goods, often unrefined, produced and distributed in large quantities for use by industry.
    * Having profit as a chief aim: a commercial book, not a scholarly tome.
    * Sponsored by an advertiser or supported by advertising: commercial television.

    The American Heritage® Dictionary of the English Language, Third Edition
    -----------------------

    Red Hat isn't sold for a price. That doesn't make it non-commercial. One of the examples above puts it best - is free to air television non commercial? As long as sales of the OS are generating revenue, not through licensing costs, but for manuals, special editions [RealServer or Oracle], product and professional certifications, etc. Basically, if it aims to make money, then its commercial.

    They can, and do, sell it commercially, but it's not a commercial product.
    You're splitting hairs. Give up. :-)
  • I just ordered this book about 2 weeks ago (it has yet to arrive) and after reading this review, I can't wait to get it! The <hushed-tone> Red Book </hushed-tone> has been one of the most useful books I've ever read, and with the addition on the new *nix variants to this new volume, it's an improvement on a masterpiece. If there is room for only one (non O'Reilly) book on your book shelf, make it this one.

    -Jason
  • Hi. I'm just curious, but being a Mac & Unix guy (gender neutral use of guy, just in case) I was wondering what you thought of Mac OS X??

    Personally I'm a Windows (3.0) to Linux guy but am really into all things *NIX (including FreeBSD) where as my wife is really a Mac person (she studies Graphic Design and Illustration etc). So I'm trying to get opinions on the true BSDness of OS X, as I think that it could solve the problem of us sharing a computer?

    So would you (or anyone else for that matter) know just how UNIXy OS X is. Apple seem to claim that the user should never need to see BSD, but if you want to can you get up to your armpits in bash shells and what not? Any thoughts would be appreciated.
  • I think that the Blue Book (O'Reilly's Unix sysadmin book) is pretty good, but it's getting pretty outdated, considering it's got a lot of OS-specific info. The Drill Book, though, is the BEST general Unix reference I've used. (I don't have the Red/Purple Book yet, but I've ordered it.) The Drill Book's coverage of shell programming is better than I've seen anywhere else. And, generally speaking, it's got so many of the answers that used to have to be answered by seasoned, full-fledged Unix gurus.

  • I'm a Sr. Network Administrator and I have two words for all those sys admins out there who would rather not pay $50+ for a book: man man

    I rarely need additional info to what the system's man pages contain (its usually acurate and up-to-date). And on Linux, which RedHat does a piss poor job of implementing, you can also browse /usr/doc and /usr/src/linux/Documentation to learn how Linux really works.

  • It is the bible for Unix System Administrators. It will help you lock down your system and get the most out of it. 'Nuff said!
  • Which O'R titles did you find obsolete?
  • I told a new admin-in-training to go get this book. The first thing he did (smart man!) was figure out if he could expense it. The first thing he did after buying it (even smarter!), was decide not to expense it, because it was going to be the core of his personal admin library.


  • uh Oh, sorry.

    I think this is a record, an non-sarcastic slashdot post!



  • Of course, stuff like god, noclip, and give just won't work; those are Quake specific.

    Quake -> Unix command conversion:

    god -> su
    noclip -> chmod 755 directory_name (directory must be executable or it will clip you)
    give -> elm -s "NEED MONEY FOR UPGRADE" ceo@company.com


  • It is traditional in book reviews to list the title of the book being reviewed, the authors, and the publisher. While from the comments it seems that some people know exactly what "The Red Book" is, I doubt I can go to my local Barnes and Noble and ask for it by that name. If you would adjust the review to include the above information, I would find it more useful.
  • The first line of the article? You mean, where it says,
    "There are a few books which most sysadmins will mention in hushed tones when discussing reading material, and one of those is the famous "Red Book", the second edition of this book (the new edition's purple). "?
    You probably meant to say the title of the post, which may or may not be the title of a book (and, in any case, was added by Slashdot - not the reviewer). My point was that a review should include title, publisher, and author in the article. The text of the review never got around to naming what it was reviewing. Simply calling it "the Red Book" is only meaningful to those who have no need of a review.

    Fortunately, one of the replies had a link to the publisher's web page.
  • The correct way of writing it according to The Open Group's Trademark Usage Guide is actually "UNIX systems".
  • Actually, at fatbrain, the old is $74.00, the new is $61.20

    go figure...

  • Many years ago I coughed up the dough for the Red Book, and I must say that it still sits on my shelf here at work. It's an indespensible reference, and I'm sure the latest edition is just as good, if not better due to it's more current coverage.

  • Re:WOW (Score:1)

    by 31: ( 144084 )
    but even better... now you can talk about 'red book' with the purple cover, and it'll just add to your aura to newbie sysadmins

    ---
    I'm not ashamed. It's the computer age, nerds are in.
    They're still in, aren't they?
  • A more complete table of contents is at the publisher's site here [phptr.com]. It's got a breakdown of the topics in each chapter. Also the preface [phptr.com] ; and the sample chapter (pdf) [phptr.com] which is Chapter 1 (Where to Start).

    By the way, does a new edition mean old ones will be available cheaper? Anyone want to give away a Red Book?

  • Re:WOW (Score:1)

    by Coz ( 178857 )
    When I "inherited" responsibility for an entire site (first guy quit, second admin was put on bed rest for her pregnancy), I ran out and bought BOTH these books. I thought they complemented one another well.
  • Thought i'd see how much Chapters was selling it for (in impoverished CAD). Mysteriously, i find under the description of that book a review reportedly by one "Jeff Michaels from Markham, ON, Canada" which contains the verbatim text from the second paragraph and a good chunk of the text from the first paragraph under What's Good. Here's the www.chapters.ca page. [chapters.ca] Scroll down a bit to see reader reviews.
  • Actually, there was the Yellow book first, then the Red and now the Purple.

    The way it's going, the next edition will be Infrared. You will need special goggles to find it on the shelf.

  • In grad school I took a unix systems administration class from Evi Nemeth (one of the authors of the book). This was 5 years ago, so we used the Red version of the book. While the book was indeed very useful, I found and continue to find that I have to look at man pages or other info on the web if I really want to know the details of how to do something with a system. Also, I think she didn't like me, because unlike the undergrads in the class, I was willing to challenge her on things (like, "Why are you always late to class, professor?")
  • I took a UNIX administration class from Evi while getting my BS in CS at the University of Colorado, Boulder and the class was strongly biased towards HP-UX, which is what all of the undergraduate labs ran. No Solaris, no IRIX, no Linux, no *BSD, no nothing except HP-UX. As far as I know Evi is still teaching there and the labs she runs are still HP-UX only.
  • Since the review doesn't say much about what's actually in the book, you can download a sample chapter in PDF format and read the table of contents at Prentice-Hall [phptr.com], the publisher of the book.
  • The book isn't a cracking tool in the least it's just a technical manual.
  • Make it kind of like an encyclopedia and sell updates to the book and have an online version. That would be really cool.
  • Plus they don't have that personal touch
  • What is with all the posts in CODE tags lately? Is that a bug in Slash or are you and this guy [slashdot.org] and the rest of you all using the same buggy browser?
  • For what it's worth, this book is only $58.95 (US) at http://www.bookpool.com.
  • ...I learned from the Quake console. It's true; the first few commands that I tried out in bash were from Quake (clear, quit, ping, status, etc.). Of course, stuff like god, noclip, and give just won't work; those are Quake specific.
  • I just wanted to correct you, you don't write "UNIXes" it's Unices. Sorry for being picky :)
  • I'm sure that this will be said a million times in this thread: If you only purchase one book, this is by far the best one out there. Period.

    I have the second and third editions of this book on the shelf next to me. My copy red bible has been read by dozens of co-workers and has become the first book that I recommend when somebody asks me what they should read in order to get started down the unix admin path. (I send them to the O'Reilly sys admin book only _after_ they have first read this one)

    This is not a book for programmers, nor is it a cookbook for those who just want to get something done real quick. This is the book you read to understand what is going on and why things work the way they do.

    I give it a 10/10. Despite the price, it is well worth it.
  • I wasn't being sarcastic.
    ---
  • True, true.
    ---
  • I think if someone can study and know everything in those books by memory, they will have a good start at unix admin-ing

    You're probably right. Being an admin does not require thinking.
    ---

  • What was your email? ryan@lovespyt.com ? Gary
  • Looks like that this would be really useful... too bad it's so expensive... Any body wanna try to open source the book... Just kidding... Wouldn't want to screw the authors out of their royalties... If I get some money in the next couple of months, I will have to get this... or put it on my Christmas list...

    Eric Gearman
    --

  • Re:WOW (Score:2)

    by Geoff ( 968 )

    I wonder, how does the reviewed book compare to "essential unix system administration" by Frisch/O'Reilly? I found the O'Reilly book rather good.

    I would recommend both. I use the Red Book (now the purple book) as the textbook for my class on Unix System Administration [wsu.edu] at Washington State University. However, I really like the Frisch book, and in fact, the way it presents info fits my thinking better. But, by emphasizing one topic at a time, the Nemeth book fits a class situation better, and makes a better reference book.

    I like the new edition. And it is so nice this semester not to need to explain all the points where the book was badly out of date (especially the chapters on sendmail and BIND).

    My only beef with the Nemeth book is that it does not cover shell scripting. The Frisch book covers the basics of Bourne shell. If the Nemeth book covered Bourne shell, it would be perfect for my class. As it is, I still use it, and just cover shell scripting separately.

  • Hmmmm...

    >ln -s /usr/bin/su /usr/bin/god
    >echo "#!/bin/sh\n\nsudo chmod -R a+rw /" > /usr/bin/noclip

  • I happen to have a copy of the 2nd edition (the red book), and have found it immensely useful and valuable. Well worth the price, especially if you're in a job where you deal with a number of unix systems, or want to be a more accomplished sysadmin. Next to O'Reilly's Unix Power Tools, this book was probably one of the best investments I ever made.

    imabug
  • I will be the first to admit that when I paid 70 for it I was uhm less than enthused. I had bought
    the previous 2 versions though and had found them
    to be still useful guides when dealing with older
    Unixs (SGI/Ultrix/OSF) that I would run into...

    The extra $30 I paid for the 3rd edition is in the
    depth they go into subjects that need to be done..
    I retired 3 O'Reilly books this week after finding
    the information not up to par with this book.

    Personally I think every support engineer and sysadmin should have a copy of this book.
  • You're quite right, of course. What was really intended there was "It's good for reading a bit of while you're stuffing food into yourself after another 12-hour day at the office, prior to slumping unconscious onto the nearest reasonably flat surface, which may or may not be a bed".

    Apologies for the confusion.
  • Yup, you're right -- I just wrote the review, and don't get anything from any sales of it as a result from Thinkgeek, Prentice-Hall or whoever. The Thinkgeek link was provided by /., not by me. The enormously positive review is simply because I love the book to bits, not for any other reason.

    By the way: Since everyone seems to be comparing the Yellow/Red/Purple books to the Armadillo Book (Frisch) -- I've got that one too, but to my mind Purple has the edge over it because it fits my mindset better. Some other people may (and do, judging by other posts) find the opposite is true for them. And yes, props to the Drill Book as well -- I've had the first edition of that sitting on my bookshelf for a long time.
  • As an AC has already pointed out, the second edition covered Solaris back in 2.3/2.4 days, when it sucked a hell of a lot more than it does now. A lot of my job involves adminning Solaris, and the Solaris-related stuff in the third edition seems pretty accurate to me. Others more guruish than I may spot more errors, of course.
  • ``1. The Red Book (this book second edition, I guess now it is the purple book)''

    I have the Yellow Book (whatever edition that was -- if it's a first edition I'll have to hang on to it, eh?). Since I'm now two colors behind I guess I should get the Purple Book now? Especially since the Yellow Book was very BSD oriented, AT&T flavors were not covered too heavily, and some newer variants weren't mentioned at all. (I think the Yellow edition came out before Linus finally got fed up with Minix. :-) )

    But US$70+??!! I think I paid about US$30 for the Yellow version.
    --

  • In my experience, the most competent Linux users were good SunOS, AT&T UNIX, SCO, or *BSD users. Good logic is timeless, as the *NIX model of command processing.

    I know this one is going on my bookshelf.
  • "UNIX System Administration Handbook" is one of the few books that I consider essential to my job. I bought a copy for myself, and then I got my employer to buy one to add to my ever-growing professional library here at work. The book really is that useful.

    The best thing about the book, to me, is the way the authors tell it to you straight. There is very little of the usual mealy-mouthed cow-towing to the Almighty Producers of Computer Products here. Instead, readers get the benefit of the authors' considerable experience and knowledge, unfiltered.

    If you're an admin and don't have this book, buy it. You'll need many other books, too, but there's no way your library can be complete without this one.
  • I was a technical reviewer for this book (my name's in the front).

    The biases against Solaris were one of my main focuses when reviewing this book. It was always a major source of contention and a big reason why I didn't recommend the previous edition to Solaris admins.

    That being said, I submitted quite a bit of corrections in this area, and I'm pleased to say that the new edition is much fairer towards Solaris.

    Also the original poster wasn't quite correct. The new edition covers many Solaris 8 issues as well. (although it doesn't go as in-depth as any general sysadmin book into nitty-gritty Solaris specifics).

  • Why if you own the second edition are you buying the third edition? Is there anything available about RedHat or BSD that could not be found out somewhere else? The point of buying this book is to get the idea of what sys admiuning should be and then there are examples regarding certain distros. The examples aren't the important part.

    Devil Ducky
  • This is be an excellent book. I started an ISP in 1994 with eight modems, two 386s, twenty Linux floppy disks and the first (yellow) edition of this book. I don't do much admin any more but I think I'll get it anyway just because it's a good read. Technical writing needs more literate authors like these guys (and the illustrations are good too).
  • I taught a chapter out of the 2nd edition, and thumbed through the rest of the book.

    It was so rife with factual errors about Solaris that I had to recommend against reading the book.

    So is the 3rd edition still this bad?

    I've been told Casper Dik (Solaris deity) met Evi Nemeth (coauthor of this book) once. I was told that approx every other sentence out of her mouth was about how much she hated Solaris.

    Granted, Sun and Solaris aren't perfect, but that's no excuse to make up things about how bad they are. That's the sort of thing that creates backlash.

  • Is "Essential UNIX administration" (O'Reilly). That's the one with the armadillo on the cover. Can't remember the name of the author, but it's probably easier to read for newbies than the famous 'Red Book'.

    A company I worked for had two (count them, two!) copies of the Red (now Purple) book -- and they were required reading for anyone who wanted to have anything to do with UNIX. And the main sysadmin kept one on his desk at all times!
  • The O'Reilly book is quite good indeed. This is even better. More importantly, though, it's different--it goes at things from a different angle, and one may present it in a way that you 'get' better than the other.

  • He didn't say Red Hat was not a commercial company, he said it wasn't a commercial OS. Learn to read.
  • Sorry, boyo, the OS itself is not commercial. They can, and do, sell it commercially, but it's not a commercial product. A fine distinction, but a distinction none the less. By the way, in this case specifically, when you 'buy' RH, you're buying manuals and support and the convenience of a CD.

  • The words I used is "good start", I didn't say one would become a guru system admin or even a decent system admin, but reading books and learning about the system is the best way IMHO to start.

    Try something. Pick a unix command, ANY unix command and key it into your console. What did you type ls or pwd? it doesn't matter what you typed. Where did you GET this commands from?

    Your memory. A admin requires fast thinking, I don't deny that. But they must also remember what does what, why and when to do it.

    Once your remember a good chunck of commands and what they do, THEN and only then, after you have remember them can you use your fast thinking and logical problem sloving to use those commands in a productive manner.

    It requires both.

    Knowledge is food for the brain and it never did anyone harm. The more knowledge you have about a certain subject is a "good start"


  • If this book is one of the Holy Books (apparently the Holiest of the Holy), what other gospels, commentaries, and books of faith on *nix would the community recommend?
  • I agree. It's pretty expensive, but luckily I found it at Borders for 30% off. :) So the book only ended up costing me about 45 bucks. Putting the cost aside, it's a pretty good book and they definately do know what they're talking about (the authors that is).
  • Actually, there was the Yellow book first, then the Red and now the Purple. I have the Yellow and Red as well as the O'Reilly and have to say Evi's book is better.

  • > The new edition is less harsh on Solaris, and saves most of its snide remarks for RedHat.

    Snide remarks towards DeadRat? More than appropriate IMNSHO. Dead Rat is a great learning tool, but you wouldn't want to risk your business on it. Too wierd, too many bits missing.

    That said, I seem to attract lots of newbies who want to be a unix admin when they grow up. I send them off to d/l the RedHat ISOs and run it up. I tell them that they should use it to learn, since loading new stuff is easy enough with the RPM thing, and it's well documented on the net.

    I qualify that recommendation with the instruction that once they have it grokked, they need to fdisk/newfs and install Mandrake (or, if they're sufficiently clued newbies) FreeBSD. Mandrake's a good home PC or an economy class server. FreeBSD's business class.

    When the newsbies come back clued, and start asking what books they should buy, I tell them The Red Book. I've never seen a better book on Unix Admin for the pre-clued. Never leave home without it.

    My copy of the red book has travelled with me to Singapore, Indonesia, Japan, Korea, New Zealand (from Australia). It's more important to me than that pesky American Express card that every retailer on the planet hates!!!

    Slightly different approach: When they ask about security, I send them out to buy:

    1) The Red Book - good grounding in *nix for the pre-clued
    2) The Crab Book (TCP/IP Net Admin - Hunt) - good for TCP/IP clues
    3) The Cricket Book (DNS and Bind - Liu) - 'If something is wrong with your net connection, first check DNS, DNS, and then DNS'
    4) 'Firewalls and Internet Security' - Cheswick and Bellovin. Needs no introduction. The network security bible. Brilliant teaching book.
    5) 'Intranet Security' - Mccarthy - Usefull for putting fear of god (and thus extracting money) from management. Also an excellent grass roots 'this is what we're on about' for newbie security types...

    My twenty-five cents...

    Geoff

  • I think it goes without saying that the Ultimate *Nix Systems Admin Handbook, heck, the Ultimate Systems Admin Handbook period, is the BOFH [ntk.net]. (Also available here [theregister.co.uk] and here [iinet.net.au])

    I think all of us can relate

  • Where *do* the reviewers get these ideas?? (Score:3)

    by devphil ( 51341 ) on Tuesday November 07, 2000 @07:30AM (#642391) Homepage


    and the writing has a light touch which makes it extremely readable both as a desk reference and as bedtime reading.

    You know, as a sysadmin, I usually don't have time to sleep. And when I do have time, I usually don't need to read anything to help me get to sleep. And when I do need to read, the last thing I want is more stuff to do with my job! I'm in home and in bed to get away from lusers! Not to think about them some more!

    For the humor-impaired: this posting has been a joke. Thank you.

  • Re:Where *do* the reviewers get these ideas?? (Score:3)

    by grondu ( 239962 ) on Tuesday November 07, 2000 @07:38AM (#642392)
    and the writing has a light touch which makes it extremely readable both as a desk reference and as bedtime reading.

    He didn't want to say "it's readable when you're on the crapper".

  • WOW (Score:4)

    by jbarnett ( 127033 ) on Tuesday November 07, 2000 @07:14AM (#642393) Homepage

    The RED Book revisted! Seriously, if you want to become a Unix admin, there are 4 books you must study.

    1. The Red Book (this book second edition, I guess now it is the purple book)

    2. The Blue Book (O'Rielly's Unix System Admin book)

    3. The Small Book (The Unix Philosophy by Mike Gancarz published by Digital Press)

    4. The Drill Book (O'Rielly's Unix Power Tools, picture of drill on front).

    I think if someone can study and know everything in those books by memory, they will have a good start at unix admin-ing. Also need a good book on your unix of choice, the man pages, and more than anything using the system.

    The point being, this book is famous, it is a really good book and is required reading for anyone wanting to get into unix admin-ing.

    I can't believe they changed the color! The 2 admin books where the red and blue books. Now it will be the purple and blue books, that isn't as catchy.

    There is also a DOD red book on security and IBM produces a lot of "red books", so it gets confusing, but most admin know what you are talking about.

    I paid I think $90 for this book at borders. It was worth it.


  • I can't do my job without this book. (Score:5)

    by SoupIsGood Food ( 1179 ) on Tuesday November 07, 2000 @07:24AM (#642394)
    I administrate a mixed shop of 70 or so systems: big HP-UX, Sun and AIX development machines with FreeBSD, Debian and a few stranger things running our infrastructure. Even tho the USAH only directly covers half the systems I have to handle, it lays down a solid groundwork =any= admin of =any= Unix system can benefit from.

    The USAH saved my hash on more than one occasion, and it really bailed me out when I first wound up a professional Unix admin. You gotta realize, I'm a Mac guy...first computer was a Mac, I now write for an up-and-coming Mac webzine, and I carry my Powerbook around with me wherever I go.

    So I was hired as the "IT Guy" by a small R&D company on the strength of my Mac skills. There were a dozen or so Macs in sales and marketing...and over 110 Sun workstations. From an old Sun 3 to a pretty monumental dual-UltraII clone, we had unix boxes running everything from our firewall and company web site to file servers and backup systems to circuit simulators and code compilers. As someone who's only experience to the comand line was a dial-in shell to get internet email, I was completely out of my league, and desparate to hold onto the job for reasons I won't get into here.

    It was a =really= hairy situation, and I kept my head above water only because of this excellent book. Now I do the Unix thing as my main career, and use the Mac for fun and personal computing. I picked up O'Reily's Systems Administration Handbook, as well as Sun's own Solaris books, but they weren't anywhere near as concise or accurate as the USAH.

    SoupIsGood Food

  • A Word of Warning (Score:5)

    by kniedzw ( 65484 ) on Tuesday November 07, 2000 @08:33AM (#642395)

    As a UNIX system administrator myself, I have to say that I have used the Red Book countless times, and it's saved me almost every time. I rarely have to look in another book (except perhaps the Frisch book, aka the "Blue Book," aka the "Armadillo Book"). What distressed me about this newest edition of the book is that they focus only on four OSs: FreeBSD, RedHat 6.2, Solaris 7, and HP-UX 11.00. While these are perhaps representative of the most popular UNIXes out there presently (with the exception of perhaps AIX), the authors made the conscious decision not to cover all of the OSs they had done before. The second edition, for instance, went over Solaris 2.4, HP-UX 9.0, IRIX 5.2, SunOS 4.1.3, DEC's OSF/1 2.0 (which is now Compaq Tru64), and BSD/OS 1.1.

    For system administrators who are interested in supporting legacy systems, the Red Book (or, more specifically, the Second Edition) is still useful. I, for instance, needed to know how IRIX set up their /etc/exports or /etc/dfs/dfstab equivalent, and I was able to find it in seconds in the Red Book. No longer.

    Otherwise, having now read the Purple Book cover to cover, I can recommend it heartily. It has the same style, flavor, and philosophy which has made the Red Book invaluable to me in the past, and I suspect that I'll be carrying around the Purple Book for years to come. Go buy it.

    Note also that you can find /.'s review of the Red Book here [slashdot.org], if you're curious.

Slashdot Top Deals

It is easier to write an incorrect program than understand a correct one.

Close