Reddit Reddit reviews UNIX and Linux System Administration Handbook (5th Edition)

We found 47 Reddit comments about UNIX and Linux System Administration Handbook (5th Edition). Here are the top ones, ranked by their Reddit score.

Cloud Computing
Networking & Cloud Computing
Computers & Technology
UNIX and Linux System Administration Handbook (5th Edition)
Check price on Amazon

47 Reddit comments about UNIX and Linux System Administration Handbook (5th Edition):

u/mu71l473d · 23 pointsr/sysadmin
  • The Practice of System and Network Administration, Third Edition
  • UNIX and Linux System Administration Handbook, Fifth Edition
  • The Practice of Cloud System Administration: DevOps and SRE Practices for Web Services, Volume 2, First Edition
  • Windows Server 2016 Unleashed, First edition
u/sfltech · 13 pointsr/redhat

I've mentored several Junior linux team members and I always recommend :

While not RH specific, it is has a wealth of information on Linux in general and serves as a good reference.

u/jgeusebroek · 12 pointsr/sysadmin

UNIX and Linux System Administration Handbook (5th Edition)

I can definitely recommend this book

u/8fingerlouie · 11 pointsr/linuxmasterrace

man pages really are good enough once you got the basics down. They were 20 years ago, and I don’t think the quality has decreased. If you want truly great man pages, FreeBSD is the place to go.

To get the basics down, start with something like this

Once you understand that, follow up with something like this

Young people today.. they pick Arch to “learn something” (or just to be cool - I can’t decide), and when the learning part starts, they want the answers served without any effort.
There’s nothing wrong with wanting to learn, just don’t expect to be finished in 4 hours.

I’ve spent 20 years as a Unix system administrator and/or developed systems running on Unix. Before I had kids I spent a few years working on Stampede Linux. My first Linux distribution was “Yggdrasil Plug&Play Linux fall ‘93”. I still learn new stuff frequently, and it usually starts with something I find on the internet, which then get tried on my own machine, and finally i use man pages for troubleshooting/fine tuning.

If that fails, I do what everybody else does, i ask google, and if I still can’t solve the issue, I will ask somewhere. Last issue I had was Debian <-> FreeBSD NFSv4 mounts with Kerberos that would freeze frequently. I spent a couple of weeks debugging that before asking, and learned a great deal in the process. After google started returning only purple links, I finally asked on a couple of forums.

u/ojimeco · 10 pointsr/linuxadmin
u/zoredache · 6 pointsr/ansible

There almost certainly no configuration management system or orchestration system guides that are going to be useful without at least a base understanding of the systems you will be managing.

If you want some base knowledge maybe start with something like this

u/Knighthawkbro · 6 pointsr/linuxadmin

Honestly, you are never going to find a way to shortcut you out of this situation. No one answer is going to be perfect and get you from A to B if your already at C. I had a similar experience with programming and web development.

I studied computer networking all my adult life and never thought I would be developing as my career at the moment. It is the burden of knowing too much and not having a clear direction. What I needed was more confidence in my skills which can only really develop over the years through experience.

You say you already know a lot of Linux and Bash concepts. CD/CI pipelines try to abstract a lot of OS related involvement since your code doesn’t need to know how low level kernel operations are happening.

What it sounds like you need is knowledge of OS concepts, not just Linux concepts. I say this because every OS has its own way of doing the same thing one way or another.

For example virtual memory, if you understand the concept of virtual memory in any OS rather than a specific OS’s semantics regarding Virtual memory then I think you would be better off in the long run.

If I am wrong and you are the master of the Linux environment, I believe you just need to deep dive into development strategies and the core principles of CD/CI. Once you have a foundation it doesn’t really mater if you are a Jenkins expert or CircleCI expert, all that matters is if you have a foundation to fall back on.

Edit: if you wanted my two cents on material here are some books I recommend.

The Practice of System and Network Administration

Operating Systems Concepts

UNIX and Linux System Administration Handbook

u/jerseylegend · 5 pointsr/devops

I can't quite envision a devops engineer without a good foundation of linux, especially if 98% of the servers are linux based. I also ask some basic scripting questions(if they tell me they do script). If the interviewee has never scripted, that's unfortunate. If you struggle moving around the infrastructure, it's going to be a difficult and stressful job, and more importantly, more work for us if we underestimated his/her skills and we have to babysit to help someone on what we perceive is essential and crucial to function. We do have numerous tools, processes, etc in aws, especially now where more and more companies are migrating to the cloud and doing serverless, but I have found that some of the bigger(little older) companies have tons of linux hosts to manage. And many of those aws resources are prob ec2's - you can ssh in, you can't escape linux!

I personally don't care which linux you know, i care more that you know how it works. However I am particular to CentOS, and Ansible.

I've had to interview a few people recently and i ask them sub-groups of questions: AWS, linux, networking, tools (jenkins, docker, config management). My hardest questions are linux. The tools, with the exception of docker, are the least significant because they can be learned; Generally the good linux candidates, for example, probably have already written scripts that do some of the functionality a config management tool was designed for. I think networking is very important but my questions are very basic. Generally the people with the aws cert/xp have already seen a lot of aws networking; Fortunately for the candidates, Ops manages the vpc's, acls, sg, routes etc so the devs don't break anything and therefore we don't rely on too much networking knowledge. But you gotta know how systems are communicating with each other.

My linux, aws, and networking(most) questions are scenario/exercise/conceptual based on real world problems/scenarios i've seen throughout the career. I simply ask what they've done with config management and jenkins or other CI and other tools they have listed on their resume.

On a maybe unrelated note - in my personal opinion, i think devops eng should learn how to use docker and know it a little in depth. It is an invaluable tool especially for development/testing work. Docker Up & Running and Docker In Practice are very good books

I'm in nyc, if it matters.

I recommend Unix and Linux System Administration Handbook The first 6 chapters (skip2) are a good start.

u/dwleonard · 5 pointsr/sysadmin

I'm a big fan of:

Disclaimer: I know 2 of the authors, but the book is still solid.

u/pat_trick · 4 pointsr/sysadmin

If you end up in the Linux / Unix world, I'd recommend the Unix and Linux System Administration Handbook...which is apparently due out in a 5th edition in just a few days!

u/slkth · 4 pointsr/linuxadmin

These might be goods books:

  1. How Linux Works, 2nd Edition (What Every Superuser Should Know) by Brian Ward
  2. UNIX and Linux System Administration Handbook (5th Edition) by Evi Nemeth, Garth Snyder, Trent R. Hein & Ben Whaley

    Book 1 I have hard copy is a quite elobarate but not too big and quite cheap. (got it for 18 dollars)
    Book 2 Is an extensive UNIX bible I really would like to have. It costs more but it's very big. A PDF might come handy.
u/vekrin · 3 pointsr/linux

Around my office this is known as our bible: UNIX and Linux System Administration Handbook (5th Edition)

It might be overkill as some of the topics aren't important if you aren't working as an engineer or devops.

Check out the table of contents and summary it might be interesting. It's one of the best no nonsense safari books out there.

u/0x4c47 · 3 pointsr/linuxquestions

Yes. It's getting in touch with many different applications and services because you need them for some project. That's how you learn. Of course if you want to learn KVM virtualization you can read a book about it and do some project on that specific topic.

If you want to get an overview of Linux and Unix administration and many different pieces of software, you could look into this book:
(DM me on how to get it)

u/almostdvs · 3 pointsr/sysadmin

First, read our Wiki. It is very thorough and answers a lot of these common questions such as

day to day? The Practice of System and Network Administration
And the topical reference books listed below.

Books to help in shaping a sysadmin? The above &:
The Phoenix Project
Time Management for System Administrators

Topical Books I see mentioned often and have been very helpful to me:
Powershell in a month of lunches
Learn Python the hard way
Unix and Linux System Administration Handbook
Windows Server 2016: Inside Out

Group Policy
FreeBSD mastery:ZFS
Pro Puppet
SSH Mastery

On my docket:
FreeBSD Mastery: Advanced ZFS

Michael W. Lucas and Thomas Limoncelli are very good sysadmin writers, you can't go wrong with a topic they have chosen to write about.

Most of the *nix stuff assumes a baseline knowledge of how to use a unix-based system. I learned as I went but did pick up an old copy of Unix Visual Quickstart Guide not too long ago at a used books sale, which seems like a good starting place for someone overwhelmed with sitting at a terminal and being productive.
I notice I don't have any Virtualization books, perhaps someone else can fill in good books. Most of my knowledge regarding virtualization and network storage has been a mix of official docs, video training, and poking at it. Seems innate but it isn't.

u/Clemlar · 3 pointsr/sysadmin

Honestly, this is by far one of the best books I’ve read and should help get you started:

UNIX and Linux System Administration Handbook

u/Medicalizawhat · 3 pointsr/learnprogramming

The easiest way to get going is to install Linux in a VM. You can do a lot in a little VM lab, spin up multiple machines, make them talk to each other, mess around with configuration management etc. Just be sure to give each machine a tiny amount of memory, maybe 500MB to a Gig.

Personally I'd recommend Ubuntu as a good first start. This is a pretty good book to get started with Linux and System Administration.

If you want to spin up a machine that is accessible from the Internet you can use a provider like AWS pretty cheaply.

Some ideas of projects involving a server could be:

  • host a website
  • set up a mail server
  • build a home media server
u/OhCmonMan · 3 pointsr/linuxhardware

Don't worry about compatibility, get Ubuntu here (for example):

Install it, play around and read some stuff. /r/linux4noobs /r/linux_tutorials, /r/linuxquestions for example. Or watch some stuff
or go crazy (highly recommended)

u/uptimefordays · 3 pointsr/sysadmin

In no particular order:

u/kramer314 · 3 pointsr/linux is super high quality (and free! although if you have the money I think it's well worth donating and / or purchasing a hard copy)

I also like and

u/dmbuddy · 2 pointsr/linuxadmin

I really enjoyed both of these books when I was starting out. Even now they are super helpful.

If you don’t know Linux at all the 2nd book gives you a good overview of things.

u/warpigg · 2 pointsr/sysadmin

Best book IMO that will get you everything start and finish in Linux AND be a great future reference:

UNIX and Linux System Administration Handbook (get the latest edition - I think its 5th ed)

Also I like the Linux Foundation certs - same folks that employ Linus. They are very good (read: hard as RH certs) now and allow you to take Ubuntu or RH as distro to take the exam in . Plus cheaper and free retake. Linux Foundation

HOwever best practice is to work with it over and over practice building/installing web servers, databases , mail servers, docker etc etc. Learn vi, learn to search on command line, bash etc.

u/OdinTheHugger · 2 pointsr/sysadmin

Advice to noobies:

  • If you're the book learning type buy this book
    I use it myself all the time as a reference if nothing else.

  • If you're the experience learning type stand up a series of VMs, and test out whatever tools you expect to be working with.

  • Learn the bare basics of ansible, the command line tool, or even just ssh-agent, it'll help a lot when managing multiple servers/instances

    What I wish someone had told me:

  • Unless the environment has EXCELLENT documentation going in, don't blindly trust ANYTHING. Be prepared to audit your servers and be sure to note down any interesting running services, if you don't know what they are or how they work, that's your homework.

    explaination: I ran into a job where the manager believed things worked in a specific way, with specific servers handling specific things, but no substantial documentation... During my time there I personally found more than 60 VMs and 4-5 physical servers that no one but the previous sysadmin had known about.

    Turns out most of those servers and VMs were a combination of things vital to business processes, but a very small handful of them were very creative attempts at establishing a backdoor into company systems, or 'temporary workarounds' that had become production critical services without proper authentication.

  • Other than that, be prepared to google. Every environment is different, within the open source and Linux communities there are 100s of ways to solve any particular problem, each with tradeoffs and requirements, it may seem daunting but if you're smart enough to ask for advice before starting the job? You'll be just fine.

  • This is a simple script that displays all user's cron jobs, this will absolutely come in handy, run it against all servers under your purview to find out if there's any hidden magic at work.
u/z-oid · 2 pointsr/linux4noobs

Not exactly what you want to hear, but the best way to learn the shell is by doing. Reading can give you a good base knowledge, but application is key.

This is by far the best way I've found to learn Linux quickly. Install Linux onto a extra computer, dual boot, or pick up a raspberry pi. Try things out, when you can't figure something out look it up. If you still can't find the answer head over to #linux on freenode. (Or Distro specific channels like #fedora #ubuntu etc.)

HOWEVER! I DO have a phenomenal book suggestion for you.

u/GaloisField · 2 pointsr/linuxquestions

See how you feel about this one: UNIX and Linux System Administration Handbook (5th Edition)


Otherwise, you little cannot go wrong with O'Reilly's "In a Nutshell" books.

u/gfever · 1 pointr/cscareerquestions

Robert Martin books are good read "Clean Code" and his architecture book.

Learn design patterns: Head First Design Patterns: A Brain-Friendly Guide

Supplement with leetcode: Elements of programming interviews

You need some linux in your life:

Get some system design knowledge:

You need some CI/CD knowledge: The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations

u/baseball44121 · 1 pointr/cscareerquestions

The issue with DevOps is it's a ridiculously broad term. I get messages on linkedin on everything from Sys Admin, to CI/CD stuff, cloud automation, SRE/PRE/*RE, and software developer.

It's weird and kinda difficult to hire for depending on the person you're looking for.

Tell him not to worry about the degree requirements on job postings though. He should pick up a good Linux book, learning networking (covered in that book), and check out open source projects that use CI/CD pipelines to try and understand how they work.

u/Avaholic92 · 1 pointr/linux4noobs

Unix and Linux System Administration Handbook is always on my desk


I would go through LinuxAcademy’s course on How to Get a Linux Job.

The down side is you’re probably not going to be a sysadmin out of the gate unless you already hold an IT job. SysAdmins usually warrant 3+ years of experience in the field in various other positions.

I started as a repair tech and have worked my way up to sysadmin status.

My day to day consists of email management to dns and everything in between. I work for a web host so my daily tasks may differ from an environment you may potentially work in.

It boils down to,

What is your skill set ?
How much experience do you have?
Can you handle yourself with minimal to no handholding depending on the environment? I say minimal here because some environments I’ve seen are heavily customized and you have to reverse engineer things to figure out how it all works together.

u/createthiscom · 1 pointr/linux4noobs

I'm not sure what you're having trouble with. You talk about networks and firewalls, LAMP setup, disk encryption, backups, etc.

I get the feeling this is an emotional outburst type post, and that's fine, but I'm not good at emotional support. You'll need to ask a specific question to receive a helpful answer.

You can literally google for any problem these days and have a high rate of success. However, if you're looking for a ground up explanation of *nix along with some history for perspective, I recommend the UNIX and Linux System Administrator's handbook:

It was the one book that helped me understand where all of this stuff came from when I got started.

However, for specific issues (bacula, for example), you'll do better asking specific questions.

u/jonythunder · 1 pointr/linuxmint

As a general starting point for linux in general, this is usually a good starting point, especially for the linux geek who might not have a structured education in Systems Administration. It also includes some tips that might be helpful should you wish to try to get a job in the area

u/BadCorvid · 1 pointr/devops

Start him with for the basic Linux admin stuff. Then teach him bash and git. Those are long term basics. Anything else gets learned on the fly.

After he has those pretty well on the way, start on whatever higher level scripting language you use, plus your configuration manager, CI/CD and in-house cloud fads (infra, containers, orchestrators, etc.)

Let him know that the "common" stuff changes every two years, so he'll have to learn new languages and technologies constantly as the fad of the month changes. It still beats Windows helldesk and unscrewing .pst files.

u/archover · 1 pointr/archlinux

I saw this:

> to connect to a PPTP vpn

and remember reading this:

> PPTP (Point-to-Point Tunneling Protocol) was developed and placed into service in the mid-1990s. While reasonably fast, it is no longer considered reasonably secure.

From as referred to in the great book Unix and Linux System Administration

It wasn't your immediate issue but just wanted to mention it.

Glad you got your problem fixed though.

u/lilSalty · 1 pointr/sysadmin

I also recently got the job. I cannot recommend this enough:

u/SweatyAcademic · 1 pointr/linux

>shell prompt

If you have money, this one is a good option

These two are good and available for free, I suggest you start with them.

> administration

This one is the best.

u/Druz1k · 1 pointr/sysadmin

The more popular book around for learning Linux is going to be the UNIX and Linux System Administration Handbook found here: If you are specifically looking to learn about everything CentOS or RHEL, my personal preference is to get this book here: which includes modules that you can complete as you read the guide (and it prepares you for the certification if you want to get it). The author of the book uses CentOS since they are basically the same OS (and it's free). My $0.02 on the matter.

u/lazyant · 1 pointr/devops

For Linux internals read , you only need the intro to each chapter (before he gets to code).

For general Linux read

You need to know some concepts very well, like life of a process and signals (may not pass initial screen interview without those), as well as basic networking (both google and facebook have a networking interview although it’s valued less than the others).

Btw there’s also an interview about designing a distributed systems, best source to learn is to read about tools at google, facebook and AWS.

For troubleshooting, there’s no book, it’s all practice with real problems. If I had the time or rather the priority, I’ll publish a bunch of broken things in docker containers as exercises but it’s a lot of work.

I do have a troubleshooting framework , with things like verify given information, trying to break the problem space in two , do first easy quick tests etc

u/youfuckedupdude · 1 pointr/linux4noobs


I would say if you just want to learn the basics of Linux the best way of doing it is using the free resources. When you find an area that interests you, thats when you dish out for the specific textbooks.

There is no shame in googling something while you're on-site or at the office. I fucking encourage it.

u/greengobblin911 · 1 pointr/linuxquestions

Many people may disagree with me, but as a Linux user on the younger side of the spectrum, I have to say there was one thing that really worked for me to finally switch for good- books.

There's tons of wikis and forums and of course Reddit to ask questions, but it is hard to get good answers. You may end up paying for books (unless you look on the internet for books) but it doesn't beat having a hard copy in front of you. It boils down to a time vs money trade off. The only wiki I would follow is one directly from the developers that act as documentation, not a community wiki. Also worth nothing certain wikis are more tied to linux and the kernel than others, meaning some are comparable/interchangable with the distro you may be using. Still, a novice would not easily put this together.

Forums are also useless unless you have the configuration mentioned in the post or that forum curates tutorials from a specific build they showcase and you as a user decided to build your system to their specifications. There's way too many variables trying to follow online guides, some of which may be out of date.

This i've realized is very true with things like Iommu grouping and PCI Passthrough for kernel based virtual machines. At that point you start modifying in your root directory, things like your kernel booting parameters and what drivers or hardware you're gonna bind or unbind from your system. While that does boil down to having the right hardware, you have to know what you're digging into your kernel for if you dont follow a guide with the same exact parts that are being passthrough or the cpus or chipsets are different.

Books are especially handy when you have a borked system, like you're in a bash prompt or an initramfs prompt or grub and need to get into a bootable part of the system. Linux takes practice. Sometimes its easier to page through a book than to search through forums.

Another thing about being an intermediate or expert Linux user is that you don't care much about distros or what other users or communities do. It wont matter as under the hood it's all the same, spare the desktop and the package managers. Once you're out of that mentality you just care about getting whatever you want done. I'm not one of those guys that's super gung-ho FOSS and open source. I just use what gets the job done. Also from a security perspective, yes Linux is in theory MORE secure but anything can be hardened or left vulnerable. It's more configuration tied than many uses and forums or threads lead it on to be.

My workload involves talking to servers and quite a bit of programming and scripting, in a variety of capacities. That's what led me to linux over the competitors, but I'm not so prudent to never ever want to use the competitor again or have a computer with it. With understanding Linux more, I use it more as a tool than to be part of the philosophy or community, though that enthusiasm pushes for new developments in the kernel.

I'm assuming you're a novice but comfortable enough in linux to get through certain things:

In any computer related thing, always TEST a deployment or feature first- From your linux system, use KVM or Virtualbox/vmware to spin up a few linux VMs, could even be a copy of your current image. This way any tweaks or things you want to test or try out is in an environment you can start over in.

The quickest way to "intermediate-expert" Linux IMO is learning system administration.

My go to book for this is "The Unix and Linux System Administration Handbook 5th edition"

This edition is updated recently to cover newer kernel features such as could environments and virtualization. This book also helps when learning BSD based stuff such as MacOS or FreeBSD.

Another good read for a "quick and dirty" understanding of Linux is "Linux Basics for Hackers" It does focus on a very niche distro and talks about tools that are not on all Linux systems BUT it does a good concise overview of intermediate things related to Linux (despite being called a beginners book).

There's also "How Linux works" but I cannot vouch for this book from personal use, I see it posted across various threads often. Never read this particular one myself.


If you want a more programming oriented approach, if you're confortable with the C language, then you can always look at these books:

The Linux Programming Interface

Unix Network Programming VOL 1.

Advanced Programming in the Unix Environment

These books would take you to understanding the kernel level processes and make your own and modify your own system.

As many have mentioned, you can go into these things with "Linux from scratch" but it's also feasible to do Linux from scratch by copy/pasting commands. Unless you tinker and fail at certain things (hence do it on a vm before doing it to the main system) you won't learn properly. I think the sysadmin approach is "safer" of the two options but to each their own.

u/admiralspark · 1 pointr/linux_mentor

Online courses: RHCSA

Books....hmmm. UNIX and Linux System Administration Handbook (5th Edition)

But honestly, I could write up a crash course for selinux and iptables. I should host a blog somewhere.

EDIT: Forgot the most important parts, /r/selinux and /r/linuxadmin !