A Comprehensive Guide to Crucial Linux Terminology: Unveiling the Meanings of Distributions, Desktops Environments, Repos, and More

Are you new to Linux and feeling overwhelmed by all the jargon in the software stores, forums, and tutorials? Fear not, as in this article, I’ll explain essential Linux terminologies so you can confidently take part in Linux discussions.

The Linux Kernel

The Linux Kernel is the primary interface for all hardware-software interactions on your Linux operating system (OS). It enables software applications to efficiently utilize system hardware like processors, memory, peripherals, and more.

It’s updated regularly to patch security issues, add support for new hardware, and occasionally remove support for outdated and unused architectures. For instance, support for AMD’s Ryzen CPUs was added with Linux Kernel version 4.10 . Older Kernel versions would experience problems running the processor.

To check your system’s Linux Kernel version, type “uname -r” in the terminal.

While some Linux distributions automatically update the kernel, others may require a manual OS update to access the latest version. As a rule of thumb, if you aren’t running bleeding-edge hardware, you should be fine with the default kernel version and routine updates you receive from your Linux distros.

Linux Distributions (Distros)

Linux distributions, or distros, are tailored operating systems built around the Linux Kernel, targeting specific users or user preferences. The term “distribution” stems from the early days of Linux, when people and organizations adopted the Linux kernel, bundled in additional tools and software–package managers, desktop environments, custom tweaks—and “distributed” it as a fully functional and cohesive operating system.

Each Linux distro offers a unique out-of-the-box experience, thus favoring certain workflows over others. For example, Ubuntu is a stable general-purpose distro, whereas Garuda Linux is focused on gaming and cutting-edge software.

Close

New to Linux? Ubuntu Isn’t Your Only Option

Desktop Environments (DE)

A desktop environment is a collection of components that build the common graphical user interface (GUI). This includes icons, panels, taskbars, wallpapers, widgets, and, most importantly, the window manager–a system software that controls the placement and appearance of application windows.

Unless you need a “headless” server , it’s super important to focus on the DE while picking a Linux distro. It’ll dictate how you open apps, multitask, customize the appearance, and more.

Click here

Close

Also, a desktop environment will come with a set of integrated apps and utilities so that the apps and overall system follow the same design philosophy and look visually consistent. For example, the GNOME desktop environment ships with GTK apps, while KDE Plasma has Qt apps. As such, if you run GTK (or GNOME) apps on a KDE system, it may feel out of place with the rest of the desktop.

4. Terminal and Console

In modern Linux computing, a terminal or “terminal emulator” refers to the GUI window that creates a command-line interface (CLI) for you to enter commands and view the system-generated outputs. For instance, here’s the GNOME terminal that’s accessible on distros running on GNOME:

In contrast, a console or “virtual console” is a special type of terminal you get in minimal GUI-less Linux installations or server environments. This gives you direct access to the shell (a command-line interpreter), offering a straightforward, full-screen CLI experience. Many Linux distros allow you to access the “console” view through dedicated key combinations–either Alt+F1…F5 or Ctrl+Alt+F1…F5.

5. Binaries, Packages, Dependencies, and Repositories (Repos)

Binaries are computer-readable code for a program (or part of a program) that the computer can run and process. Packages are binaries bundled with additional information such as configuration files, version numbers, software descriptions, installation instructions, dependencies, and more. Now, dependencies for a package are additional packages, binaries, or system components, necessary for that package to run.

Different distros have their own packaging formats for creating distro specific software packages, like Steam, LibreOffice, or Firefox. They upload these packages to a large library called a repository so you can easily download and install them. For example, Debian and Debian-based distros support DEB packages which are maintained in the Debian repository .

Now, sometimes, the software you want won’t be in the official repository, at which point you can reference an unofficial collection called a third-party repository. For reference, Personal Package Archives (PPAs) is a third-party repo for DEB packages maintained by program developers or enthusiasts.

Take this example: I’m trying to install LibreOffice , but it isn’t available in the Ubuntu 22.04 repository. So I had to add the PPA:libreoffice, where it’s available to install.

Only use PPAs from trusted sources (check reviews and ratings) to avoid installing malware on your system.

6. Package Managers

Package managers are tools that connect you to a software repository so you can easily download, install, update, remove, and manage packages along with their dependencies. Just like packaging formats, there are distro-specific package managers. For example, there’s APT for managing DEB packages on Debian-based systems and DNF for managing RPM packages for Red Hat-based systems.

This mode of distributing packages can be challenging for developers as they have to package their apps into multiple formats and keep them updated on multiple repositories to ensure availability across distros. To try solving this problem we have universal package managers like Snap and Flatpak.

Close

Universal package managers distribute software that includes everything necessary to run it, making it easier to install and compatible with different distros. Moreover, they require minimal interaction with your system files, making them theoretically more secure. However, by bundling “all” necessary files, universal packages are more extensive and take up more space.

Prioritize installing apps in the official repo because they are optimized for your system and take up less space. Use Snaps and Flatpaks when official repo packages are not available.

7. Rolling Release and Point Release Model

When looking into different Linux distros, you must have come across the terms “rolling release” and “point release”. This basically refers to how updates are delivered to a distro.

In a rolling release model, your Linux distro gets continuous updates to the latest software. This means you’ll always have access to the newest features and fixes. However, updating your system regularly (at least every two weeks) is essential to avoid compatibility issues with future updates. If you don’t, your system might become outdated. Examples include Manjaro and Garuda Linux.

Close

Point release distros release new versions at specific intervals. You don’t need to update your system as frequently, which can be convenient for professionals or servers that require stability. These releases, called “upgrades,” update many core system files or replace them with newer packages. Examples include Ubuntu, Pop!_OS, and Linux Mint.

Close

Point release distros have an “End of Life” date. After this date, they no longer receive updates, which can lead to security risks and compatibility issues if you keep using them. For example, Ubuntu 23.10 is supported for 9 months after its release, while Ubuntu 22.04 LTS (Long Term Support) gets 5 years of support.

Understanding these essential Linux terms is the first step towards becoming a Linux power user. With this knowledge, you’re now better equipped to navigate the Linux landscape, engage in discussions, and confidently continue your learning journey.

Also read: