I never read the original USAH so I have to ask: does this cover specific programs present on specific systems, or is it more of a philosophical guide to being a sysadmin?
My observation is that the recent direction of Fedora (which has been followed relatively closely by Ubuntu, RHEL, SUSE, etc.) has been diverging from traditional UNIX, as far as system administration tasks go. SysVinit is being replaced with systemd. You've got plymouth and kernel mode-setting for boot, instead of a text-mode console. PolicyKit runs a daemon that manages permissions and controls what apps can do. /dev/dsp has gone the way of the dinosaur, with another daemon -- pulseaudio -- taking its place. Then there's virtualization, which everybody does differently.
The evolution of the userspace plumbing layer of Linux over the past 10 years will change the way sysadmins have to deal with common tasks. The old ways may no longer suffice. Many books will be written about RHEL 6.
If the book doesn't cover the new RHEL 6 concepts -- for example PolicyKit, which has been around since F9 and is an important new technology to learn for system administration -- then it might have limited value as a practical guide to people who are using newer distros. But if it isn't meant to be a practical guide anyhow, then that's cool, too.
Just remember that a lot of the new technologies growing up in current Linux distros are evolutionary spinoffs of UNIX design. Some of them fit perfectly into UNIX philosophy, while others suggest a new direction -- sometimes Windows-like, and sometimes a unique new design altogether.
Author interview: UNIX and Linux System Administration Handbook
Posted Jul 13, 2010 18:21 UTC (Tue) by dowdle (subscriber, #659)
[Link]
Amazon seems to have a significant chunk of this book available for viewing online so anyone interested, have a look.
I do NOT see newer topics like PolicyKit and pulseaudio. Given the fact that systemd is a proposed feature for Fedora 14 and isn't done yet... I wouldn't expect this book to cover it. Of course they cover SysV. Upstart and SELinux are also covered.
I teach a Sysadmin Class once a year and I've asked for an eval copy of this book since I am looking for a text... as I was previously trying to save the students the cost of a text... and using primarily the RHEL Deployment guide, a few other free texts, and man pages. This book does seem really nice.
Author interview: UNIX and Linux System Administration Handbook
Posted Jul 13, 2010 20:09 UTC (Tue) by jebba (✭ supporter ✭, #4439)
[Link]
Previous editions covered such concerns as how many BTUs a sysadmin generates so you can calculate cooling for your data center... While it may not cover pulseaudio (I haven't seen the latest edition), it does cover real-world issues not touched by other books. I read the 2nd and 3rd editions cover-to-cover...
Author interview: UNIX and Linux System Administration Handbook
Posted Jul 15, 2010 12:25 UTC (Thu) by nix (subscriber, #2304)
[Link]
how many BTUs a sysadmin generates
You mean 'system', right? I would assume that as long as your sysadmins are human beings they generate the same amount of heat as any other human being...
Author interview: UNIX and Linux System Administration Handbook
Posted Jul 15, 2010 17:07 UTC (Thu) by jebba (✭ supporter ✭, #4439)
[Link]
I meant sysadmins or whoever is in the data center.
Author interview: UNIX and Linux System Administration Handbook
Posted Sep 24, 2011 16:23 UTC (Sat) by Baylink (guest, #755)
[Link]
While the writers of this series of books don't ignore the philosophy of systems and network administration, they are definitely practical, hands on, commandline books at their heart.
If you're looking for what and why, rather than when and how, you should really check out (if you haven't already seen it), The Practice of Systems and Network Administration, by Limoncelli, Hogan, and Chalup, or TPOSANA. This book tells you almost nothing about what to type at the command line; it's focus is at 30,000ft, rather than 500. And it is *excellent*; anyone who's anywhere near admin management or supervision, even informally, should read it every 6 months.