Linux Help

“Linux” isn’t the actual OS you use, it’s more like the underlying framework (we call it a kernel) that other people can then add components onto to make the full operating system. Those components are stuff like the package manager (how you download software), the desktop environment (like the visual way Windows and Mac look), the under-the-hood stuff that handles running all the scripts on boot that need to run, and everything that runs in the background while your computer is on. So the “Distros” (Linux Distributions) below are essentially the full “OS” organized and bundled together by either a community, a community, or sometimes an individual. If you install a Distro like Arch Linux, then you’re basically choosing each of these components manually to build your own OS, whereas something like Ubuntu is created by a corporation as a complete OS, like Windows.

Best for Windows users who want something to “just work”

• Linux Mint – best option for non-technical users
• ZorinOS – a little flashier and less tested, but apparently a very pain-free experience

Best for users who want more control and are down for tinkering

• Fedora Linux – what I use daily, has lots of support
• Ubuntu – made by a corpo who has opinions. Like the Apple of Linux (derogatory), but also widely supported
• CachyOS – most optimized for NVidia GPUs

Best for a console-like experience only for playing games

• Bazzite – extremely stable experience designed to look and feel like a video game console, works great for a living room/couch experience
• Nobara – similar to Bazzite, with a limited, simplified experience, but a bit more tailored toward regular desktop use

Update mid-2026: GNOME is not that stable these days, stick to KDE unless you need GNOME for something. Cosmic is a better pick than GNOME right now if you want something more out there.

Desktop Environments are the actual look and feel of your computer. The Distro will control the behind-the-scenes stuff, but most Distros use one of two DEs:

• KDE – more “Windows”-y, lightweight, a “traditional” desktop
• GNOME – more “Mac”-y, flashier, nice for laptops/trackpad

There are actually lots more DEs, but unless the distro you choose uses another one, then you’ll probably end up picking up one of these. For example, Fedora lets you choose GNOME or KDE, but Mint comes with Cinnamon, it’s own dedicated DE.

Basically, if you are using a laptop or want something that feels fresh, then try GNOME, otherwise, KDE will feel familiar. If you choose a Distro whose main DE isn’t one of these two (Like Mint/Cinnamon), then just use the default one, as it’s probably why you chose that distro in the first place.

Mostly, nah, but sometimes you’ll actually find it easier, like instead of having to actually search for a setting on a specific page, nested behind clicking on a bunch of other pages, with like 20 steps to get there… you just open a terminal and paste a command or two and problem solved. Better yet, since basically everything CAN be done via commands, you can make easy shortcuts to repeat commands later, without needing to open the terminal, just by running an app.

But yes, there will be times when your only option is to interact with a terminal. Some Distros will try to minimize this, like unless you’re doing something technical, you shouldn’t need to open a terminal in Linux Mint 99% of the time.

When you do find yourself needing a terminal, you’ll want to be aware of some basic command-line-interface (CLI) tools, or just “commands”. Stuff like navigating directories, making folders, deleting files, etc., and other logic things like what pipes “|” are for, when and when not to use sudo, and how to make a bash script.

• Common CLI Commands – has most commonly used commands. The top has a table with the names of commands and what they do, then below it details every single one, explaining deeper, showing the syntax, with common options and examples, along with what the example actually does. There’s even a section for common errors at the very bottom.
• Command Lookup – this site will let you type any command, and will give you a description of what it does, give you a bunch of examples for common uses with different options, and point you towards more detailed official documentation if needed
• Bash Scripting getting started guide – if you want to make a script that runs multiple commands for you, or even just one, but from a simple executable app, then you’ll want to make a bash file (.sh, a shell script), to store those commands. It doesn’t just have to be a simple flow from one command to another either, it can have logic like if statements with branching conditions, or checking if previous commands executing successfully before continuing.
  • Bash advanced cheat sheet