#linux administration

Since first typing the ls command on a fresh Ubuntu install back in 2005, I was immediately confronted with how little I knew about this emerging open source OS called Linux. The NOC admins quickly corrected my approach and had me reinstall with Fedora Core 5. That is where the real fun began.

From there, mastering Linux became a passion that has challenged me for years. I had some UNIX exposure from my military days, accessing personnel publications and working with postal mail systems, but I was never an administrator.

Somehow, a Microsoft Word document has followed me through my career. It was eventually converted to OpenOffice in keeping with open source philosophy. Every time I learned a new Linux task, I documented it there. This file has traveled via Gmail across various jobs, saved me from countless jams, and constantly evolves. No version numbers, just the latest email in my sent items. That is my version control.

I find Stack Overflow spammy and often unhelpful with rude dead ends, so this personal document became my primary resource. If you are like me, man pages can be cumbersome when you are first learning an application. I admire those who can read them like children’s books. God bless you, I am still trying to keep up!

During recent downtime, I have been converting this document into micro-articles on my public GitHub. It is a living document, so updates will always continue and are even updated to the latest systemd standards.

I have always called it “Mr. System Admin”, not as an egotistical claim, but as a humble joke about what I aspire to be. Will I ever truly become “Mr. System Admin”? Probably not, as my age reminds me. I likely have about seven years left in IT before handing things off to the Gen Z folks gradually taking my place.

I am now maintaining this decades-old document on GitHub for anyone facing similar challenges. Warning: This is for the humble, for those not afraid to admit weaknesses. If you are the type to over-criticize, this document is not for you. It serves as a portable resource for contractors navigating complex scenarios. I hope it serves others as faithfully as it has served me during my journey with this beautiful operating system. Keep in mind that system configurations vary, and scripting or commands may need adjustments, but this guide should consistently put you in the right ballpark.

Side note: The book that truly elevated my skills was “UNIX and Linux System Administration Handbook” by Evi Nemeth and Garth Snyder.

Advanced Infrastructure Automation with RHCE, and Terraform

What I will learn?

Manage complex Linux systems.

Automate infrastructure using Terraform.

Implement DevOps workflows.

Material Includes

 Terraform guides and templates.

 Study materials and Guides.

 RHCE certification voucher.

Requirements

 RHCSA or equivalent knowledge

We are always ready to help you and answer your questions

Email Us

[email protected]

Bangalore

+91 72044 31703 +91 80959 33365

Hyderabad

+91 77993 51640 +91 90597 64550

BTM Layout – Bengaluru

A 401 error means the server refuses access because authentication failed or wasn’t provided. It’s the web’s way of saying “you’re not authorized.” Learn what causes it, how to fix it, and why understanding this error helps keep your site secure and accessible.

Master the find command in Linux. It's essential for anyone working with Linux systems. This detailed guide will show you how to use the find command to search for files and directories based on name, size, date, permissions, and more. You will learn how to combine multiple conditions, execute actions on found files, and optimize searches for better performance. As a system administrator, developer, or advanced user, you need to understand the find command in Linux. This will make managing and automating your workflows faster, more efficient, and more powerful.