{"canonical_url":"https://engineer.company/glossary/ubuntu/","content_markdown":"# Ubuntu\n\n## What it is\n\nUbuntu is a Linux distribution published by Canonical: the Linux kernel and the\nthousands of programs around it, built, tested and patched by one publisher on a\ncalendar it announces in advance. It is derived from Debian, so it uses the same\n`.deb` packages and the same `apt` tool to install them, and it adds its own\nrelease rhythm, its own defaults and a company that sells support. The same\narchive feeds desktops, cloud images and bare-metal servers; this entry is about\nthe server.\n\nReleases are named after the year and month they shipped, so 24.04 came out in\nApril 2024. A new one appears every six months, and every second year the April\nrelease is a long-term support release, marked LTS. The difference is the length\nof the promise. An interim release gets nine months of fixes. An LTS release\ngets five years of standard security maintenance, which an Ubuntu Pro\nsubscription extends to ten through Expanded Security Maintenance, and a Legacy\nadd-on to fifteen.\n\nOn servers Ubuntu is usually weighed against two neighbours. Debian is its\nparent: the same packaging, with a community project rather than a company\nbehind it. Red Hat Enterprise Linux and its rebuilds, such as AlmaLinux and\nRocky Linux, form the other family, with their own package format and their own\ntools. Choosing among the three is mostly choosing a calendar, a support\ncontract and the habits the team already has.\n\n## Why it matters\n\nOnce a team has picked Ubuntu, the decision that remains is which Ubuntu, and\nthat decision sets the maintenance budget for years.\n\nServers belong on LTS releases. An interim release expires nine months after it\nships, so a server that tracks them has to go through a release upgrade twice a\nyear to stay patched, which is a lot of change for the privilege of slightly\nnewer packages. Interim releases are where you try what the next LTS will bring.\n\nAn LTS release has a firm upgrade path, and it is narrower than people expect. A\nserver moves from one LTS to the next one only, without skipping any: from 20.04\nthe way to 24.04 runs through 22.04. The release tool, `do-release-upgrade`,\noffers the jump only after the new release's first point release, so 24.04\nbecame the default upgrade target once 24.04.1 was out. A fleet that falls two\nreleases behind therefore needs two full upgrades per machine, each with its own\ntesting.\n\nUbuntu Pro is the other half of the decision. It adds the five extra years of\nsecurity fixes, Livepatch for applying kernel fixes without a reboot, Landscape\nfor managing machines as a fleet, and FIPS 140-3 and CIS hardening tooling for\nregulated work. It is free on up to five machines, which covers a small business\nor a lab; beyond that it is a paid subscription. The honest comparison is the\nsubscription against the cost of upgrading on schedule. Five years is enough for\na server that gets rebuilt from code; ten years suits the appliance nobody wants\nto touch, where paying for patches beats migrating in a hurry.\n\nFinally, Ubuntu has its own way of doing ordinary things, and a team arriving\nfrom another distribution should budget time to learn them. Network interfaces\nare configured in YAML through Netplan. The firewall is usually managed through\n`ufw`, a front end that ships disabled. Security updates install themselves\nevery day through `unattended-upgrades`, which is on by default. Each of these\nis pleasant once known and surprising before.\n\n## What it looks like in practice\n\nA fleet of Ubuntu Linux VPS instances that had grown one machine at a time is\nthe clearest picture of what an unmanaged estate turns into. The configurations\nhad drifted apart, and nobody had designed how the machines would be recovered\nor how they were networked. The work\n[brought all thirty instances under management as one fleet](/portfolio/managed-30-ubuntu-linux-vps-instances/):\nbackups went in with restore procedures that were actually tested, and every\ninstance's network configuration was moved onto the same hardened baseline.\nRecovery paths were now tested rather than assumed, and the downtime risk\ndropped.\n\nDatabases ran on the same footing elsewhere. Ten servers running PostgreSQL 14\nand MS SQL Server 2019 on Ubuntu 20.04 LTS VPS instances were\n[designed, deployed and maintained](/portfolio/ran-10-postgresql-and-ms-sql-servers-on-ubuntu/)\nas one estate. Backups ran through `pg_dump` and SQL Server Agent jobs, with\nretention policies and offsite storage. Prometheus and Grafana tracked CPU,\nmemory, disk I/O and query metrics. Both the databases and the Ubuntu OS were\npatched on a regular schedule, the firewalls were configured with UFW, and\naccess was enforced with role-based access control. Disaster recovery was\ndocumented down to point-in-time restores and failover. The ten servers ran at\n99.9% uptime, query response times improved by 30%, automation cut manual\nmaintenance by 50% and freed more than ten hours a month, and the estate\nabsorbed a 40% rise in user traffic without degrading.\n\nWeb hosting is the plainest case.\n[Forty websites ran on Ubuntu Linux hosting servers](/portfolio/administered-40-websites-on-apache-and-nginx/)\nbehind a mix of Apache and Nginx, and the job was the configuration, the\nperformance tuning and the maintenance that keeps sites reliable under real\ntraffic. All forty ran with high availability and good performance.\n\n## Where it goes wrong\n\n**The updater installs a kernel fix, and the server goes on running the old\nkernel.** `unattended-upgrades` installs security updates once a day, but its\n`Automatic-Reboot` option defaults to false, so a new kernel waits on disk until\nsomeone restarts the machine, and services keep using the old copies of updated\nlibraries until they restart too. The file `/var/run/reboot-required` appears\nwhen a reboot is pending. Decide on a policy instead of leaving it to chance:\nalert on that file, schedule reboots in a quiet hour, or use Livepatch for the\nkernel. A scheduled reboot is two lines in\n`/etc/apt/apt.conf.d/50unattended-upgrades`:\n\n```text\nUnattended-Upgrade::Automatic-Reboot \"true\";\nUnattended-Upgrade::Automatic-Reboot-Time \"03:30\";\n```\n\n**A server on an old LTS release stops getting security fixes while everything\non it keeps working.** Standard support for 20.04, for example, ended in May\n2025; the machine boots, serves and reports green exactly as before. Record each\nserver's release next to its end-of-support date, and before that date either\nattach Ubuntu Pro, which carries 20.04 to May 2030, or upgrade one LTS at a\ntime.\n\n**A new `ufw` rule goes in, and traffic flows exactly as before.** `ufw`\nevaluates rules in order and the first match wins, and a plain `ufw allow` or\n`ufw deny` lands after the rules already there. An older, broader rule above it\ndecides first. List the rules with their positions and put the specific rule\nwhere it belongs:\n\n```sh\nsudo ufw status numbered\nsudo ufw insert 1 deny from 203.0.113.7\n```\n\n**A package from a third-party repository stays on an old, vulnerable version\nwhile the rest of the system is current.** `unattended-upgrades` installs only\nfrom the origins listed in its `Allowed-Origins` setting, and out of the box\nthat list holds only official Ubuntu repositories. A vendor repository or a PPA\nadded later is updated by hand or not at all. Add its origin to the list\ndeliberately, or put that package on a patch schedule of its own.\n\n## Further reading\n\n- [Ubuntu Server documentation](https://ubuntu.com/server/docs)\n  — Canonical's own guides for installing, configuring and running Ubuntu on\n  servers.\n- [Ubuntu release cycle](https://ubuntu.com/about/release-cycle)\n  — the six-month cadence, the LTS calendar and the end date of every release.\n- [Automatic updates](https://documentation.ubuntu.com/server/how-to/software/automatic-updates/)\n  — how `unattended-upgrades` chooses origins, and the reboot options that\n  decide when fixes take effect.\n- [Firewall](https://documentation.ubuntu.com/server/how-to/security/firewalls/)\n  — `ufw` from first enable to numbered rules, with the netfilter layer\n  underneath.\n- [How to upgrade your Ubuntu release](https://documentation.ubuntu.com/server/how-to/software/upgrade-your-release/)\n  — `do-release-upgrade`, the one-LTS-at-a-time rule and the point-release wait.\n- [Netplan documentation](https://netplan.readthedocs.io/en/stable/)\n  — the YAML network configuration Ubuntu servers use, including `netplan try`\n  with its automatic rollback.\n\n\u003chttps://engineer.company/glossary/ubuntu/\u003e\n","date_modified":"2026-10-20T21:59:50Z","description":"Which Ubuntu belongs on a server: LTS or interim, when Ubuntu Pro pays for itself, how release upgrades work, and the reboot the updater leaves to you.","formats":{"gemtext":"https://engineer.company/glossary/ubuntu/index.gmi","gopher":"https://engineer.company/glossary/ubuntu/gophermap","html":"https://engineer.company/glossary/ubuntu/","json":"https://engineer.company/glossary/ubuntu/index.json","markdown":"https://engineer.company/glossary/ubuntu/index.md","pdf":"https://engineer.company/glossary/ubuntu/index.pdf"},"kind":"page","language":"en","title":"What is Ubuntu?","url":"https://engineer.company/glossary/ubuntu/","version":1}