A repository of useful exercises to learn the very basics of Systems Administration.

• A computer capable of "virtualization" (i.e. running a virtual machine)
• Administrative (aka "Admin" or "root") access to your computer
• An internet connection (large parts of this documentation will require downloading and installing software from the internet)

I, the original author, as well as any contributor will not be personally liable or responsible for irreparable damage to your computer up to and including:

• Data such as photos, videos, music, documents, etc. stored on your computer(s)
• Retention ("backup") of aforementioned data
• OS settings or configuration
• Any related/applicable changes to your computer made during the course of engaging in these exercises

That being said: I'm envisioning this as a community effort. As a result, I intend to make Good Faith Efforts to help people who ask for it.

In short:

• Backup your data (external hard-drives are your friend)
• Have patience (things inevitably will break or go wrong)
• Ask for help if you need it (everyone needs help once in a while)

A few friends had been asking me about where they might start to learn the basics of how to become a Systems Administrator really get their career in technology moving. A couple of them have been in retail and customer-facing roles and are looking to move out of that role. In authoring this, I want to enable them as well as anyone else looking to make a move or improve their skills:

• People who have worked with computers, but don't understand the finer points of running a system or a platform
• People who have worked in other departments or adjacent fields who are looking to expand their skills
• People who are curious and want to poke around (hobbyists/tinkerers)

TL;DR: This repo is for anyone who's looking to make a move into basic systems administration.

• Linux OS Basics
• Client/Server fundamentals
• Linux Server fundamentals
• Networking fundamentals
• Internet fundamentals

The other reason being that flexing my writing ability through authoring public-facing documentation to help others indirectly helps my ability to communicate with other team members, teams, stakeholders, etc. much more effectively. So, a little bit of self-directed skill-building.

By breaking this topic down into two (perhaps more in the future) separate tracks, Linux and Windows, I feel as though not only can people choose the path(s) they want to follow, they can also work at their own pace.

Discussion in the repo's Issues section is a good place to start. Feel free to submit Issues for consideration and discussion!

Basically:

1. File an Issue
2. Make changes on a fork
3. Submit a Pull Request (PR)

Thanks!