• The first start-to-finish guide to patching Linux systems in production environments
• For Red Hat, Fedora, SUSE, Debian, and other leading distributions
• Comprehensive coverage of apt, yum, Red Hat Network, YaST Online Update, Zenworks Linux Management, and other tools
• High-efficiency techniques that minimize impacts on networks, users, and administrators

The Start-to-Finish Patch Management Guide for Every Linux® Environment

To keep your Linux systems secure, reliable, and productive, you must stay current with patches and updates. But, until now, it has been difficult to find usable, trustworthy guidance on managing patches in Linux production environments. Linux Patch Management fills that gap, offering Linux professionals start-to-finish solutions, strategies, and examples for every environment, from single computers to enterprise-class networks.

Michael Jang presents patching solutions for Red Hat, Fedora, SUSE, Debian, and other distributions. He systematically covers both distribution-specific tools and widely used community tools, such as apt and yum. This book’s streamlined patch management techniques minimize impacts on users, networks, and administrators, and address applications as well as the underlying OS. Whatever your role in managing Linux systems, Linux Patch Management will reduce your costs, enhance the availability of your systems, and dramatically improve your personal efficiency.

• Consolidating patches on a Red Hat network, including cached updates, as well as patching systems based on RHEL rebuild distributions
• Working with SUSE’s update systems, including YaST Online Update and Zenworks Linux Management
• Making the most of apt commands and the GUI-based Synaptic Package Manager
• Configuring apt for RPM distributions such as Fedora and SUSE Linux
• Creating repositories that can manage gigabytes of patches on diverse Linux systems
• Updating networks of Linux computers without overloading WAN or Internet connections
• Configuring yum clients, including coverage of emerging GUI tools such as Yum Extender

Bruce Perens’ Open Source Series is a definitive series of Linux and open source books by the world’s leading Linux professionals. Bruce Perens is the primary author of The Open Source Definition, the formative document of the open source movement, and the former Debian GNU/Linux Project Leader.

Series Editor Bruce Perens is an open source evangelist, developer, and consultant whose software is a major component of most commercial embedded Linux offerings. He founded or cofounded Linux Standard Base, Open Source Initiative, and Software in the Public Interest. As Debian GNU/Linux Project Leader, he was instrumental in getting the system on two U.S. space shuttle flights.

© Copyright Pearson Education. All rights reserved.

About The Author

Michael Jang holds RHCE, SAIR Linux Certified Professional, CompTIA Linux+ Professional, and MCP certifications, and has written books on four Linux certifications. Specializing in networks and operating systems, he has two more books coming soon: Linux Annoyances for Geeks (O’Reilly, 2006) and Mastering Red Hat Fedora Linux 5 (Sybex, 2006).

© Copyright Pearson Education. All rights reserved.

Customer Reviews & Comments
My first reaction to this was negative. What the heck do you need a book on this subject for - aren't the man pages enough? Then I waffled a little - maybe it is nice to have the 10,000 foot overview of all of this, mixed in with some useful advice. I'm still not sure. If you are managing multiple systems or are a consultant who is apt to run into most anything, this could be very helpful. For the average Linux user, maybe not: in my experience such people either leave their systems alone (no updates at all) or are themselves expert and keep their systems perfectly current - the latter probably don't need this. But I still have that nagging doubt. For my own machines in my own office, I vacillate horribly. I always do the updates after an initial install, but often I ignore them after that unless it's some very serious security issue that I can't ignore. I do this because I don't want to break my systems and often I just don't have time to stage and test things.. but on the other hand sometimes I get religious and keep on top of a box weekly. So.. I remain unsure of this book's value to me, but I'll keep it around as insurance. Comment | Permalink | (Report this)