Top products from r/linuxadmin

We found 69 product mentions on r/linuxadmin. We ranked the 105 resulting products by number of redditors who mentioned them. Here are the top 20.

Next page

Top comments that mention products on r/linuxadmin:

u/robscomputer · 2 pointsr/linuxadmin

A few of my favorite books I reference and recommend. Just a note, many of these are older and can be purchased used for much less. Also if you can afford it, get a Safari subscription. I use my work Safari subscription but this alone has saved me from my book buying habit. Now I only buy "must have" books. :)

Official Ubuntu Server book - I really like this book as the writing style helped me "get it" with Linux. Kyle Rankin has a very good method of showing you the technology and then a quick run down to get the server working, followed by some admin tips. It's a just scratching the surface type of book but it's enough to get you started. I rarely use Ubuntu now, but this book helped me understand DNS and other topics that were IMHO harder to grasp from other books.

As a bonus, this book also has an entire chapter dedicated to troubleshooting. While this sounds obvious, it's a great read as it talks about dividing the problem, how to approach the facts, etc. Stuff a seasoned admin would know but might be hard to explain to a new admin.

The Linux Command Line: A Complete Introduction - You can read this book for free on the site, but having a paper copy is nice. As mentioned, you should have a very solid understanding of the command line. In my experience, I have seen co-workers struggle with basic shell scripting and even understanding how to make a single line for loop. This book covers the basics, moving to shell scripting and I think it's a good solid reference guide as well.

DevOps Troubleshooting: Linux Server Best Practices - This book is referenced a few times here but I'll throw another comment for it. Another book from Kyle Rankin and has the same straight to the point writing style. It's very quick reference and simple enough that you could give this to a new sysadmin and he or she could get started with some of the basic tools. While the book covers a good selection of basic services and tools, it's easy to get deeper into a chapter and find it's only discussing a handful of troubleshooting steps. The idea with this book is it's a quick reference guide, and if you want to get deeper into troubleshooting or performance, take a look at other books on the market. Either way, this is a great book I keep on my desk or reference through Safari.

UNIX and Linux System Administration Handbook (4th Edition) - Another popular book based on the comments here. This is a pretty big book, thin pages, but it's like a small brick of UNIX/Linux knowledge. While it's starting to get dated, it does give a great reference to many topics in the system administration world. The chapters can dive deep into the subject and offer more than enough information to get started but also understand the technology. The e-mail chapter I thought was great as well as the DNS. I think of this book as a overall guide and if I want to know more, I would read a book just on the subject, that's if I need more information. One thing to point out is this book makes use of different OS's so it's filled with references to Solaris, different UNIX versions, etc. Not a problem but just keep in mind the author may be talking about something outside the scope of vanilla Linux.

Shell Scripting: Expert Recipes for Linux, Bash and more - I found this book to be a good extenstion of the Linux Command Line book, but there are many many other Bash/Shell scripting books out there. The author has many of the topics discussed on his site but the book is a good reference for scripting. I can't stress enough how important shell scripting is. While it's good to know a more formal language like Python/Perl/etc, you are almost certain bash will be on the machine you are working on.

Systems Performance: Enterprise and the Cloud - I can't comment on this book beyond the first chapter, I'm still reading it now but it's reading similar to Brendan Gregg's site, and that's a great thing. If you don't know who this guy is, he's one of the top performance guys in the Solaris and now Linux world. He has some great infographics on his site, which I use for reference.

Use method for Linux

Linux Performance

Example of Linux performance monitoring tools

Hope this helps!

u/coniferhugger · 2 pointsr/linuxadmin

Instead of buying tons of books, you might want to look at Safari Books. I have the 10-book bookshelf subscription, and it is seriously plenty. Pros, you have instant access to a massive library of tech books. Cons, you are stuck reading on your computer/tablet/phone (I did try reading a few chapters on my Kindle, but the didn't care for the experience).

Books I would suggest:

  • UNIX and Linux System Administration Handbook - this is seriously a great book, that will make any admin better.
  • Time Management for Systems Administrators - has a lot of good tips for time management, but some things are a little dated.
  • The Practice of System and Network Administration, Second Edition - This is a great read on how to be a better system administrator.

    I'm not a huge fan of training videos, but generally watch recordings from conferences. Although, I do really enjoy the format of vimcasts though.

    As for general advise, I did see someone recommend looking for an MSP. If you are looking to be a Linux SysAdmin, I wouldn't recommend this route as you are going to be supporting MS installations. Personally, I started doing help desk for a web company and moved up from there. Also, I worked hard to create my opportunities within each position. You'll have to put yourself out there and be patient, It took me 4 years to earn the official title of Systems Administrator (in a small-ish town). The key to this is finding a good Sr. SysAdmins who are willing to mentor you, and some environments/people aren't conducive to this.


    BTW, I have a B.A. in Political Science, so don't be ashamed to rock that Philosophy degree. You will see a lot of posting that are looking for a B.S. in Computer Science/Computer Engineering/Rocket Surgery, but seriously don't even worry about that. Most job postings are a list of nice to haves, and most places really only care that you have a degree.

    I've been recruited by and interviewed with some very respectable tech companies. I just usually have to explain how I got into tech with a political science degree. In an interview, having the right attitude and knowing your stuff should say more than your major in college. But, you will also run into elitist douche bags who knock your degree/doubt your abilities because you don't have a B.S. in CS/CE. If you work with these people, your work should speak for itself. Don't try and get caught up into a pissing match with them. If it is an interview (as in someone you might work for), practice interviewing never hurts.
u/timlepes · 1 pointr/linuxadmin

I few years ago my youngest brother got his first IT job, and he fell right into an admin role. He too is very sharp. I bought him the following books as a gift to get him started...

The Practice of System and Network Administration, SecondEdition - a few years old but has lots of fundamentals in there, still well worth reading. Hoping for a third edition someday.

Tom Limoncelli's Time Management for System Administrators

I see others have recommended this great book, and I wholehartedly agree: UNIX and Linux System Adminstration, 4th Edition. I was sad when Evi's ship was lost at sea last year. :-( You could tell she loved sailing old wooden ships... just look at the cover. A great loss; she did so much for our community.

Additionally, I will second or third anyone recommending works by Brendan Gregg. I got the Kindle version of Brendan's Systems Performance: Enterprise and the Cloud. I really like this book. It was written to be a good foundational book for the next several years. I am planning to get a hard copy version too. While you're at it, check out these links...

Brendan Gregg:

Tom Limoncelli:

Introduce him not only to books, but online resources and communities like /r/linuxadmin :-)


u/solid7 · 9 pointsr/linuxadmin

A lot of what has been suggested is great for learning linux. Realize that "out there" very little is served out of a single box (and if it is you're doin it wrong). Production infrastructure likely looks and acts very very differently from your home linux workstation. Just because you know how to type sudo apt-get install apache2 does not mean you are ready for a full ops position... BUT - if you put in the wrench time and pay your dues, you will get there.

Here are some areas that would be good to build your knoweldgebase up in...

  • First and foremost - you must build the ability to learn how to figure things out and build an intuition of what to inspect should something not be working. This comes from having a working knowledge of many different systems in a large heterogeneous environment. This will come with experience.
  • Learn some of the rapid deployment frameworks - cobbler, puppet, cfengine, etc... No one sits around configuring each and every production machine from scratch.
  • Now that you are familiar with (presumably) the installation and configuration of apache, start thinking about setting up caching/proxy infrastructure. Get a sense for what to use for load balancing v.s. caching v.s. increasing availability (and some combination of the three). Become familiar with things such as nginx, mod_proxy, haproxy, squid, varnish, mongrel, etc...
  • You MUST know how dns works. Crickets bind and dns should be considered required reading. Any lack of understanding of how dns works is simply unacceptable for a proper sysadmin.
  • this book is required reading, period.
  • You must become familiar with centralized authentication mechanisms. Most systems utilize something called PAM. Learn how to configure PAM to reference slapd, AD, etc... Kerberos is our current preferred central authentication mechanism, you need to know how to bounce kerberos tickets around. Get slapd (OpenLDAP) up on its legs.
  • When running a linux kernel, learn how to configure netfilter. Under linux, Netfilter is the thing responsible for routing, nat, and packet filtering. Understand that other kernels do not use netfilter (or commonly use something else). Become familiar with the common kernels firewall, routing, and forwarding system(s). Don't make the mistake of saying "the iptables firewall..." in the interview room! Iptables is not a firewall.
  • Know your basic networking. Internet core protocols should be added to your list of required reading. Understand the differences between a hub, bridge, switch, and router. Learn how to "subnet", which means knowing your binary math! I cannot tell you how many times I have seen a messed up network because someone didn't know how to figure out /27 and keyed in the wrong values from a "subnet calculator". Along with networking do a bunch of reading/research on vlans, trunking and stp. Most people cannot tell you what a L2/3 managed switch is or how it differs from a "dumb" switch or router. Don't be one of those people! Learn how to configure routing protocols such as BGP, RIP and OSPF (also, learn basic computational graph theory). You may not end up doing a whole lot of networking, but it's really good stuff to know.
  • Virtualization is important. You need to know the different forms of virtualization (desktop v.s. os-level v.s. para v.s. hyper virtualization). If you are keen to linux, you need to know how xen and kvm work (this is typically what commercial vps's typically use). Also look at vmware and virtualbox for desktop virt. For os-level virtualization, you need to know how to use LxC and jails.
  • Learn how LVM works! Spend some time familiarizing yourself with LVM2 (linux), vinum (BSD), and ZFS's container framework (Solaris/BSD). Know how and when to use raid. Make sure you understand the implications of the different raid configurations.
  • Learn common backup methodology. Raid is not backup, don't make this mistake.
  • Get used to doing everything on the command line, and always think "what if I had to do this on 20,000 servers?".

    So off the top of my head there's a bunch of things you could study. I think that's quite a bit to get your head around, and a deep understanding of some of these topics will only come from working experience. There may be a LOT of work to do in some of those areas. Getting a fully functional xen (or kvm) based system up and on it's legs is not an easy task for the uninitiated. It is my opinion (and everyone else is free to disagree with me) that all good sysadmins/ops/engineers need to "grow up" in some area of lower level technical position. That can be a jr. admin position, the helldesk, or whatever else... This will give you the "systems" working experience that will let you branch into a full fledged admin/op position. Getting some certs under your belt can help you get in the door, but by all means isn't required. Cert's cost money and (the ones worth getting) take time. Personally, I tend to stray away from places that make a big deal out of certs... but that's just me.

    tl;dr: Learn how to learn. Pick something you don't know how to do and leverage a linux system to accomplish that goal - rinse and repeat.
u/fuzzyfuzz · 18 pointsr/linuxadmin

I have the UNIX and LINUX System Administration Handbook It's awesome and has a pirate boat on the front, so you know it's good. It's great for best practices type stuff, and there's a little bit of sysadmin humor mixed in.

I also have the Linux Command Line and Shell Scripting Bible which is good for CLI reference.

Other than that, you can find a ton of stuff on the web. Is there anything in particular you are looking for?

u/IWentOutside · 6 pointsr/linuxadmin

While you did mention you prefer hard copies, if you want him to stay current, you should consider a subscription at as it has just about every O'Reilly book there is and you/he can always order a hard copy if desired. Otherwise High Performance MySQL 3rd Edition is pretty great, especially with explaining replication and backup/restoration procedures, as well as DevOps Troubleshooting, which has a great section on troubleshooting the boot-up process that may be useful.

u/chucky_z · 2 pointsr/linuxadmin

As an additive to this, if you cannot afford the training, the RHCSA/RHCE book by Jang is an incredible resource:

I will be taking the test when I can afford it from only studying this and real-world experience through my job.

I'd also like to add on that if you want some easy real world experience setup a cheap VPS to host websites on, this will give you a fantastic taste in troubleshooting issues, installing software, securing stuff, etc... It's also an easy way to make a small extra income. :)

u/whetu · 2 pointsr/linuxadmin

When I studied for the RHCSA, I found that Sander Van Vugt came highly recommended. Best of all? $Free (i.e. get the free trial and go for it)

I also got the Ashgar Ghori book because the Michael Jang one wasn't out yet.

Jang's RHEL6 books were highly regarded, so I would expect his RHEL7 stuff to be held in similar esteem. Ghori's book seemed perfectly capable, though.

u/j_e_f · 4 pointsr/linuxadmin

Master this and you'll become a ninja :

u/thecotton · 12 pointsr/linuxadmin

So. I read Michael Jang's RHCSA/RHCE book.

It took me 16 days to get through Ch1 - 10.
Chances are, if you can do all those things, you can get a job as a Linux Jr. Systems Administrator.

I knew nothing about Linux, read that, and -- I've been a rather successful Linux Jr Admin (soon to be Sys Admin) at my current job. It also allowed me to be an Infrastructure Director for a startup. So.

I mean. Really, knowing LAMP is half the battle. Pick a P, learn MySQL & Apache, and pick a flavor of Linux (I'm RHEL distros, obv). Master the basics, master the finer points -- and you're good to go. Having a few popular applications under your belt like puppet, aide, rkhunter, clamav (perhaps), configurations for php properly (secure) & mod_security ... a few things like that, and you're good.

u/Medicalizawhat · 2 pointsr/linuxadmin

I recently got a job as a junior admin and found Unix and Linux System Administration to be really good. There is also a nice CBT Nuggets series on Linux which is a great overview, especially when watched while reading LPI Linux Certification in a Nutshell as the book complements the videos.

If he already knows another programming language Dive Into Pythion is great for getting up to speed quickly.

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/Righteous_Dude · 2 pointsr/linuxadmin

I recommend you complete your LPIC-1 learning, whether or not you then take its exams, before starting RHCSA.

I'm currently going through this recommended book by Michael Jang to learn RHCSA and RHCE, and also this book by Sander van Vugt for RHCSA and RHCE.

In the book by Michael Jang, at the end of chapter 1, he writes that the LPIC-1 exams "cover a number of related commands that we believe are implied prerequisites for the Red Hat certifications" and also says "Passing the LPIC 101 and 102 exams provides an excellent foundation for the RHCSA and RHCE exams."

It's wise to know everything at the LPIC-1 level whether or not you choose to buy the two corresponding exams for the LPIC-1 certification. If you do want to buy & take exams to get an LPIC-1, you might as well buy & take the two current Linux+ exams, and then have them tell LPI so that you also get LPIC-1. But it doesn't work the other way (if you get LPIC-1, you don't automatically get Linux+).

u/asthealexflies · 1 pointr/linuxadmin

Agree with the comments posted by others. I would suggest the book bellow, which will give you a really nice all round grounding into all thinks *nix.

Gets the fundamentals and you can tackle any system from a good level of base knowledge. Also a great bible for the shelf.

u/bofha · 7 pointsr/linuxadmin

Tanenbaum's textbook is par for the course THE best low-level exploration of the fundamental concepts of operating systems. It is, however, HIGHLY theoretical, and requires a solid base of knowledge prior to even starting it. It also is not useful for learning specifics about every day tasks.

This is a phenomenal introduction to the concepts and some of the practice of Linux:
And here is a practical-first exploration of how to use Linux:

I would highly recommended reading these two books, then picking up a copy of Tanenbaum's, and finally this:

If you actually study and practice implementing the topics discussed in these four books then you will have a far better understanding than 90% of the Linux users I've interacted with.

u/[deleted] · 4 pointsr/linuxadmin

My personal favorite book is The Unix/Linux System Administration Handbook 4th edition. it has everything you need to know and recommended reading for more details on tasks... good way to help expand your library.

u/sanedave · 3 pointsr/linuxadmin

thrilljockey's advice is excellent. To add to that, follow the guides at and

Work through Practical Guide to Linux

This has improved my skills/knowledge in amazing ways.

u/cottonmouthbob · 1 pointr/linuxadmin

Systems Performance - Brendan Gregg

Knowledge of how Apache works, of how MySQL works, of what dhcp does on the wire: all this is good knowledge. But a more fundamental skill is troubleshooting. Troubleshooting is having an idea how something is supposed to work, tracing where it’s misbehaving and then fixing it. I suggest, for any admin, reinforce your ability to troubleshoot.

Performance tuning isn’t always necessary. On an over-provisioned system, you don’t care; just let it run and do its job. But where the study of performance tuning comes in handy is that it’s the systematic troubleshooting of systems. We measured something. Is this what we expect; why or why not? Are we really measuring what we think we’re measuring; how do we validate? What’s the system doing on the inside; how do we find out? What’s impeding this system from operating faster/better; why?

I advocate systems performance, because I think it reinforces troubleshooting. I advocate troubleshooting, because it’s the top-down, fix-my-need now, universal and adaptable approach. In this world of on-the-job training and with new technologies every six months, it’s how to approach new systems and new problems without having to start on page one of the manual every time.

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/joker_toker · 5 pointsr/linuxadmin

I'd like to humbly suggest the UNIX and Linux System Administration Handbook for your new admin. It's starting to show its age a bit (published 2010), but still communicates many of the core responsibilities of administrators in a clear manner with historical context.

Also, take a look at the Linux System Administration and Linux Web Operations LiveLessons, which are more current and may be helpful if the new guy learns from video tutorials.

Disclaimer: I am the author.

u/skapunker02 · 1 pointr/linuxadmin

I think you can only still take the test for 6 at the kiosk locations, which are more limited so depending where you're at you may have to take the 7 test anyways.

I think the Jang book is still a good resource, especially if you want to get a good foundation of preparation, just keep in mind you'll need to also familiarize yourself with the changes in 7.

This has some useful information:

u/jkurthoconnor · 1 pointr/linuxadmin

Very much not a recipe book, but I think a good fit for deeper understanding: How Linux Works

u/pThread · 6 pointsr/linuxadmin

I took RedHat's SELinux course: RHS429

It was actually pretty good. The instructor recommended the light sabre book

u/gsmalleus · 1 pointr/linuxadmin

I agree, this book is great. Although it is not targeted at any specific OS environment, it does encompass a lot of knowledge. Also, the link you provided is for the first edition. [Here is the newest edition.] (

u/mhurron · 10 pointsr/linuxadmin

or the previous edition

Both have a Linux case study after going through the details of what makes an OS.

Your not going to have a RHEL specific book of this nature because a distro like RHEL is a mash of so many different and huge projects that are under constant development. If you want to know the ins and outs of GNOME for instance, you're going to have to delve into the GNOME developer documentation, same with things like Systemd and GLIBC

u/DocPenguin01 · 3 pointsr/linuxadmin

Definitely go with RHCE. It's a hands-on lab exam vs. LPIC which is multiple-choice. If you can pass it, you prove that you actually know your way around a Linux system.

I strongly recommend this book.

I used it to it brush-up the last time I re-certed, and I've given it to two people who both passed their RHCSA on the first shot, and one who went on to pass his RHCE.

u/ihatefarts · 4 pointsr/linuxadmin

This book has saved my ass countless times. It has a bunch of great knowledge and gives you a chance to catch up on things you might have forgotten. I highly recommend you purchase this and keep beside your desk/cube, at least until you become familiar with the job duties.

u/ocf_splat · 2 pointsr/linuxadmin

You can pick yourself up an RHCSA/RHCE exam study book, like for instance, or you can just follow the online documentation and start from a blank system, then format and install the distro of you choice, then configure it and install the software of your choice (apache, mysql, python), configure the network interfaces and the firewall. I keep recommending FreeBSD, Gentoo, and Slackware as starting points. Then you might want to move on to Debian or CentOS/Scientific Linux. Linux From Scratch is good if you really want to dig deep and understand things from another level.

u/jake_morrison · 1 pointr/linuxadmin

Advanced Programming in the Unix Environment ( is also great, though not Linux specific, more traditional Unix APIs

u/delias_ · 4 pointsr/linuxadmin

Fundamentals is what you need to know to get through some first round interviews. Explain the boot process in detail from pressing the power button to getting a login prompt -- how does init work, how do run levels work, how does systemd differ? What is getty? pam?

DNS is so much more than just what that rap covers, so if you put it on your resume you better damn well know it. Tell me about the concept of glue records, what is a root hints file, know how to use dig at the very least, how do you switch the order in which the resolver library checks it sources? What is the truncated bit in a DNS packet for?

Know debugging and tracing beyond the usual "top" or "sar" to get real detailed data on what a process is doing. Strace, ltrace, tcpdump, gdb (how to take a stack trace and dump a core), sysdig, perf events, dtrace4linux, vmstat, slabtop, pmap, etc

DHCP is another one like DNS that people like to say they know, but you should know about DHCP relay/ip helper, pxeboot, the actual protocol order of events. Check it out in wireshark.

How do processes and threads differ, really? Lots to talk about here even down to shared memory space, system calls, etc

What is swap, really? What are page faults? How does kswapd behavior change when you don't run with swap?

Know Netstat/ss. Know that tcp is a state machine. What does a bunch of SYN_SENT in netstat imply? Difference between tcp's RST and FIN?

Stateful vs stateless is more than just a tcp/udp difference, it's a fundamental concept to so many aspects of technology.

Basically know what's in this book:

u/InvisibleTextArea · 7 pointsr/linuxadmin

I agree with what others have said and I also have a book recommendation, "Time Management for System Administrators". There's lots of good ideas and suggestions in it.

u/RoosterTooth · 1 pointr/linuxadmin

Good information! I also have a wonderful 1200 page book I just bought to start reading too!

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/laibr · -3 pointsr/linuxadmin

I was hoping someone ran into the same issue and it was as simple as adding a service label Or something
I’ll add some extra info later.

Ps. How bout asking this for christmas:

u/alefthandeduser · 3 pointsr/linuxadmin

The Practice of System and Network Administration by Tom Limoncelli, Christina J. Hogan and Strata R. Chalup. Each sysadmin at my current employer is bought a copy. It's not only useful, it's also interesting.

u/lazyant · 3 pointsr/linuxadmin

You may want to study this book: "Systems Performance: Enterprise and the Cloud" by Brendan Gregg

u/joedonut · 1 pointr/linuxadmin

UNIX Shells by Example by Ellie Quigley. Reviews here.

u/veruus · 12 pointsr/linuxadmin

The Practice of System and Network Administration, Second Edition

UNIX and Linux System Administration Handbook - 4th Edition

[TCP/IP Illustrated, Volume 1: The Protocols - 2nd Edition] (

These should be part of every ops department's library, if not already in your own personal one.

u/bincat · 1 pointr/linuxadmin

> * this book^1 is required reading, period.

1 (Amazon link to the first edition)

Is there a reason for the first edition suggestion or can the more recent second edition be more appropriate?

u/kerrz · 1 pointr/linuxadmin

If you're looking for a book/course-of-study, Michael Jang's RHCSA/RHCE Study Guide teaches to the RedHat exams, which are practical, hands-on technical exams (not like the multiple-choice braindump bullshit in most of the industry.)

u/cstoner · 2 pointsr/linuxadmin

Last time I remember leafing though this guy it was still very relevant.

It's a lot of basic UNIX/Linux nuts and bolts stuff.

u/aberuwork · 0 pointsr/linuxadmin

Yeah. - 2.22% Annualized Failure rate. $355.99 for 12 TB, 256MB Cache - 0.33% Annualized Failure rate. $439.98 for 14 TB, 512MB Cache.

You get what you pay for rings true.

u/mriswithe · 1 pointr/linuxadmin

The only way to know is to try the test, or practice tests/questions. This book has some of each for RHCE and RHCSA:

Exam is administered largely one of two ways:

  • Scheduled classroom style events that take place at a testing facility with a group of computers and someone in person running the exam, looking over it, etc.
  • Kiosks that you schedule a time and go and there is a single computer Kiosk. You are shown to it by a employee of whatever business runs that Kiosk, then you put your ID in a scanner and show your face to the cameras and get to work. The Kiosk I have taken the RHCE at is at a local drug testing company.

    You only get a single try. If you fail, you have to pay $400 again.
u/RainbowHearts · 2 pointsr/linuxadmin

The cloud is just other peoples' computers.

AWS, Azure, and other cloud providers give you magic cloud computers that just magically work... except they have all the same constraints and failure cases that every computer has.

Unless you understand what goes into maintaining those computers (HINT: it's traditional linux admin skills), then you will fail to design your applications and services appropriately. Your shit will break, you will scramble to find out what's wrong, and the only solution available to you will be to turn it off and back on again, or to build a new one and kill it.

If your solution is to turn it off and back on again, or terminate the instance and press the make-a-new-computer button, then you're not a sysadmin. You're a technician.

And if you're writing the dockerfiles that get hooked up to the make-a-new-computer button, that doesn't make you an infrastructure engineer. That's a technician writing the build instructions in advance.

It's UNIX / Linux all the way down. Read The Practice of System and Network Administration. Learn the old ways because without them you will not understand why the new ways are what they are.

> All the linux admin i know that is good, are excellent coder as well; they have no problem working on AWS, learning go and mess around with kubes.

Go is just a tool. Kubernetes is just a tool. AWS is just a business selling computer time.

Anyone can operate a pneumatic drill, but a dentist understands teeth and the mouth. Anyone can use CAD and make a 3-D model of a building, but an architect understands the properties of the building materials under stress.

My application may be located in AWS, but if you can't build a resilient service on bare metal then you have no business administering my system.