Read a sample: 1. Build Your Maintenance Baseline
A useful security routine begins with a simple question: What am I maintaining?
On a Linux PC, the answer is more specific than “Linux.” Your computer has a distribution, a release of that distribution, a desktop environment, and a collection of applications that may receive updates in different ways. Those details influence where you find settings, which instructions apply, and whether the system still receives security support.
This chapter helps you record those facts before changing anything. The result is a baseline: a dated snapshot you can return to when a setting changes, an update fails, or you ask someone for help. You do not need to understand every item immediately. An honest “not yet checked” is more useful than a guess.
The goal is observation, not a full security audit. Later chapters will guide you through backups, updates, accounts, software sources, the browser, and the firewall. For now, concentrate on identifying the system and recognizing anything that should not wait for a scheduled review.
Set aside a few uninterrupted minutes and sign in to the account you normally use. Open a note, a paper notebook, or another place where you can keep a dated record. If you maintain more than one computer, use a separate record for each one.
Begin with a descriptive name that will help you distinguish the machine, such as “personal laptop” or “office desktop.” Note who normally uses it and whether it is personally managed, shared, or managed by an organization. This matters because a work or school computer may have policies that you should not change on your own.
Record the date of the review. Security information has a shelf life: a supported release today will not necessarily remain supported indefinitely, and a status you checked months ago may no longer describe the computer.
Do not put passwords, recovery keys, authentication codes, or complete copies of sensitive documents in the baseline. A maintenance record should help you work safely without becoming a collection of secrets.
A Linux distribution, often called a distro, combines the Linux kernel with system components, software-management tools, and a release and support model. Examples include Ubuntu, Fedora, Debian, and Linux Mint. Related distributions can look similar while differing in their update tools, support periods, and recommended procedures.
The release identifies which version of the distribution is installed. When following instructions, the distribution name alone is often not enough: a menu or command that applies to one release may not apply to another.
Start with the graphical interface if you prefer. Look in Settings for a page named About, System, System Details, or something similar. The wording and location depend on the desktop. An application provided by the distribution may also show the operating system’s name and version.
If the graphical page is unclear, you can inspect a standard operating-system information file from a terminal:
text
cat /etc/os-release
This command displays the file; it does not change it. Look for fields such as PRETTYNAME, NAME, and VERSION. Copy the displayed distribution and release into your record. If the command reports that the file is unavailable, use the graphical information you found and consult the distribution’s documentation rather than guessing.
You may also see a kernel version in a system-information page. The kernel is an important part of Linux, but its version is not a substitute for the distribution release when checking the distribution’s support schedule. Record it if it is easy to find; it is optional for this first baseline.
The desktop environment is the graphical workspace you interact with: its panels, settings, menus, and window controls. GNOME, KDE Plasma, Xfce, and Cinnamon are examples. The same distribution can offer more than one desktop, and different distributions can use the same one.
This distinction explains why otherwise sound instructions may not match your screen. A guide might say to open a particular settings panel, but your desktop may use a different name or arrange the controls elsewhere. For desktop settings, both the distribution and the desktop environment can matter.
The About page may identify the desktop. You can also try this terminal command:
text
echo "$XDGCURRENTDESKTOP"
The result is a clue about the current graphical session, not a guaranteed, neatly formatted desktop name. It might contain more than one identifier, or it might be blank. If you are unsure, record the result as displayed and mark the desktop for follow-up. There is no need to install a tool just to complete this worksheet.
If you use a computer that opens to a command line rather than a graphical desktop, note that instead. This book focuses on desktop maintenance, but a clear description of what you see is still a useful starting point.
A system can appear to work normally after its release has stopped receiving security updates. Opening a browser or seeing a familiar desktop does not establish that the operating system remains supported.
Using the distribution and release you recorded, consult the distribution’s official documentation or release information. Look for:
- The release’s support status and the date through which the relevant security updates are provided.
- Whether the information applies to your particular edition, repositories, or support arrangement.
- The recommended path when that release approaches or reaches the end of support.
Support arrangements differ. Some releases have a short maintenance period; others have longer support, sometimes with conditions or differing coverage for components. Do not assume that a…