Slashdot Mirror
Teach Yourself UNIX System Administration In 24 Hours
The Big Picture As you might get from the title, Sams Publishing's "24 Hours" book series attempts to teach specific tasks or steps within 1 chapter per hour. UNIX can get pretty complex, so it would seem that this format would limit the effectiveness of this book. Not so.
Topics from the book include:
- Unix Installation
- Documentation
- File Ownership
- Disk Usage
- Account Management
- Package Management (including the Fink system for Darwin)
- Process and System Controls
- Network configuration
- Web Server Management and shell scripting
Almost every chapter views how a particular task is handled with Linux as its normal focus, where many commands are shared between Solaris and Mac OS X. When functionality differs, Taylor downshifts to show how matters are handled in each respective operating system. As someone very experienced with Mac OS X, I found Dave Taylor's discussions on Mac OS X idiosyncrasies in contrast to Red Hat and Solaris very useful, particularly where Darwin overrides the traditional dotfile preference configuration, substituting the convoluted NetInfo services.
What to Expect Dave provides a Q & A section after each chapter. In an early chapter, Dave answers a typical geek question, "What Unix distributions do you run on your own systems?" Dave provides a very geeky answer--his Apple PowerBook G4 is running Mac OS X (with Darwin as its core, of course), along with a PC running Windows 2000, Linux Mandrake 8.1, and a web server running Red Hat Linux 7.2--a varied assortment that shows Dave puts the author in authority. In a later chapter, Dave touches on emulators such as WINE and Virtual PC as options for additional operating system support.
What makes the book work is that Dave provides a very conversational tone throughout the book, almost as if you're sitting with him in front of a system, talking while you do your thing. Humorous moments are scattered in appropriate moments to make things less dry (this is UNIX, after all).
Questions that weren't answered for me as a beginning UNIX sysadmin in another book by Dave Taylor, Learning UNIX for Mac OS X , were available in droves in this book. Topics such as scripting with perl or from the shell, disk quotas, crontabs, rlogin, managing system logs, and the like--all answered. Ever wondered how Mac OS X handles system init states? You'll discover that its a tad different from other UNIX systems, but not too much.
The Bad and the Upshot I ran into several layout problems in the book that were somewhat annoying, such as where tables or notes were sliced between pages, making them difficult to read. It wasn't a showstopper at all, but I hope that a later reprint will pass muster.
If you're still getting your feet wet with a few basics, or have a really mixed environment of UNIX flavors, this book may be very useful to you. I'd recommend this book to any Mac OS X technician who wants to take advantage of its UNIX underpinnings. Beginning Linux users should also find this a strong general reference. The book's cost ($25) is very reasonable, even a bargain for a book of this depth. Overall, Teach Yourself Unix System Administration in 24 Hours makes for a very well rounded reference, as well as a tutorial book. Perhaps the title should be shorter--it's quite a tongue twister.
You can purchase Teach Yourself UNIX System Administration in 24 Hours from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
As a Unix sysadmin for seven years, I'd have to agree with the reviewer that this book is a lifesaver. I find that information tends to dissipate from my head after I absorb it (sort of like Mother Nature's swapping algorithm LOL), so I spend the first day of each month rereading it, and this keeps my skills charged for the rest of the month! I've even gotten pretty good at scheduling major projects for early in the month, when things are fresher in my head.
Karma: Good (despite my invention of the Karma: sig)
How many of these books can one own? I have plenty of books, but the mile-wide-but-foot-deep-overview books get old. I have Glass and Ables' "Unix for Programmers and Users" and Oreilly's "Running Linux". I reference there every so often (in fact just yesterday while installing VOCAL), but I'm not sure there is much more I could get out of a book that wasn't specifically about some library or application.
Most of the quick reference stuff anyone needs is on various websites and discussion boards.
sig
http://www.google.com/search?hl=en&lr=&ie=UTF-8&oe =UTF-8&safe=off&q=%22Dave+Taylor%22+%22Kevin+Spenc er%22
The question is, at what point does slashdot have to start adhering to standard ethics of journalism? Which is to say: the person who wrote the glowing review -- located conveniently over a link to purchase the book at bn.com -- should at least tell us he's an author of published works on the same subject... whose books are listed alongside those of the author he's lauding.
On the other hand, a book like this can never make you a GOOD systems administrator as the secret there lies in years of experience, knowing what kind of odd, twitchy little things to look for; and also knowing how to use all these neat little utilities and chain them together in the shell (of your choice) to make them do large, complicated, magical things.
A book like this might very well be the beginning of a beautiful career. The worry is that people will read it and think they're ready to tackle the world. Of course that's why we have certifications, but they only prove one's ability to regurgitate knowledge on command. Handy, but a book like this can give you just about everything non-vendor-specific that shows up on most Unix certs, I'm guessing -- and some of that, too.
On the gripping hand, it used to be matter of course that the sexretary or similar ended up being the one to maintain the mainframe, being sent to Armonk for classes... you know what I'm talking about. Maybe someday some of Unix's quirkiness will be ironed out and that sort of thing will be feasible in Unixland. I'm not holding my breath, though.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
I taught a network troubleshooting class once and had to pick between a $75 book and a $20 book. the $20 one was Teach Yourself Network Troubleshooting in 24 hours. I picked it because of price mostly (thinking of the students) and it looked pretty good. Not as much material as the $75 book - but still had a good bit in it.
It worked out very well and the students actually liked it a lot becuase it was a little funny and had good basic concepts in it.
Not trying to be an ass or anything. But you might want to hope that you sys admin is reading this book - along with others im sure - becuase if he isnt - some fellow employee in the company could be surfing thru your files right now....
Duke
FreeBSD: Nothing runs like a daemon with a pitch fork.
That's one thing that absolutely kicks ass about the opensource nix's. Everything you need to learn about nix you can learn at home for free and run them on the oldest pc's you can find.
I mean try learning windows 2000/exchange/SQL server on a P90 with 32MB ram. Not only is the software timebombed(You don't get to keep that now useful file/print/dns/proxy/firewall/blah server up running forever)but the hardware requirements are much higher.
Plus these days even though everyone wants to talk about TCO, there is something to be said for being able to provide File/Print/DNS/Web/Proxy/Database/Directory software to your company for Free. Unless your working for the most diehard of diehard MS shops employers take note of that sort of thing.
If you wanna get rich, you know that payback is a bitch
There are about a dozen keystrokes that you need to memorize, and you're productive with vi. If that takes you more than 24 hours, you should have started with a simpler task. :%! is open-ended. But the basics aren't that much to learn. Different from what most people seem to be exposed to before they get to vi, for some reason, but I think that's cultural and not technical in nature.
Of course you can keep learning vi forever, because what you type after
-fb Everything not expressly forbidden is now mandatory.
One microsecond of downtime (for a daemon re-start) re-starts the uptime clock in my book. Claiming continuous uptime just because the kernel hasn't been re-started measures very little indeed.
You can only drink 30 or 40 glasses of beer a day, no matter how rich you are.
-- Colonel Adolphus Busch
Well, I don't know about that. I took a job YEARS ago as a Novell network admin. I had Never worked novell before. Before I started the job, I read a Novell book cover to cover. First day I was productive. Other than peeking at the book every now and then, I was able to get my job done.
What DOES kinda irritate me is the "24 Hours" part. Sorry, you can't even scratch the surface in 24 hours - especially with UNIX. While I WAS productive right off the bat with Novell, my prior experience with UNIX and other networking systems allowed me to figure things out quickly. Without a good solid background, I would have been toast. I really was a "junior" novell admin. Over the next several months at that job, I felt totally comfortable doing quite advanced tasks with novell.
While you can pick up some simplistic skills in 24 hours, there is a LOT more to UNIX system administration that you just can't learn from a book, or even another administrator. You have to do things for yourself. You have to understand the concepts. You have to play with things, look around, compile some apps, install some systems, run into problems and solve them, learn scripting, regular expressions, read TONS of man pages, etc. This takes MONTHS. Most of your true learning comes from problem solving.
I do take some exception to the "learn more from a sysadmin" comment. The problem with this approach is that sysadmins FREQUENTLY are not good teachers. In fact, I find sysadmins in general to be among the WORST teachers of any profession. Working side by side with one, you will learn small little snipits of valuable stuff, but rarely will you understand the WHY of things. S/He probably isn't going to present info to you in any organized manor, and the info will most likely be very incomplete. Hey, that's just been my experience working with / managing dozens of admins - many of them VERY good at what they do.