Book Image

Linux Administration Best Practices

By : Scott Alan Miller
3.3 (3)
Book Image

Linux Administration Best Practices

3.3 (3)
By: Scott Alan Miller

Overview of this book

Linux is a well-known, open source Unix-family operating system that is the most widely used OS today. Linux looks set for a bright future for decades to come, but system administration is rarely studied beyond learning rote tasks or following vendor guidelines. To truly excel at Linux administration, you need to understand how these systems work and learn to make strategic decisions regarding them. Linux Administration Best Practices helps you to explore best practices for efficiently administering Linux systems and servers. This Linux book covers a wide variety of topics from installation and deployment through to managing permissions, with each topic beginning with an overview of the key concepts followed by practical examples of best practices and solutions. You'll find out how to approach system administration, Linux, and IT in general, put technology into proper business context, and rethink your approach to technical decision making. Finally, the book concludes by helping you to understand best practices for troubleshooting Linux systems and servers that'll enable you to grow in your career as well as in any aspect of IT and business. By the end of this Linux administration book, you'll have gained the knowledge needed to take your Linux administration skills to the next level.
Table of Contents (16 chapters)
1
Section 1: Understanding the Role of Linux System Administrator
4
Section 2: Best Practices for Linux Technologies
9
Section 3: Approaches to Effective System Administration

Sources of solutions

Where do we get the solutions to problems that arise when we are system administrators? I want to start this conversation with my own career anecdote, because I think that everyone gets very different perspectives on how IT support works in the broadest of senses and understanding different perspectives is important before we start to define what good looks like.

When I first started working in IT, and for the first nearly two decades, it was an assumption that any and all issues would be resolved by the IT department. Of course, situations existed where applying patches, updated, or fixes from a vendor would be part of the process, but acquiring those patches, testing them, applying them, and so forth were always completely handled by the IT staff. Even the idea that you could ask a vendor to assist, guide, or advise was foreign let alone attempting to actually do so. Reaching out to a vendor for support was assumed to be an absolutely last resort situation...