Ubuntu 26.04 Tutorial / Update Ubuntu and Configure Time and the Terminal

After installation, separate release identification, package-index refresh, update installation, time synchronization, and post-reboot checks. New Ubuntu 26.04 installations use chrony by default, so inspect the actual time service rather than applying older timesyncd instructions blindly.

Record the environment and resources

cat /etc/os-release
uname -r
df -h /
ip -br address
whoami

Check the installed Server’s 26.04 release, root space, account, and interfaces. New installations and upgraded systems can have different packages. Distinguish the actual distribution/kernel from the guest label in the virtualization tool.

Separate index refresh from package installation

sudo apt update
apt list --upgradable
sudo apt upgrade

apt update refreshes repository indexes; it does not upgrade installed programs. Resolve index errors first, review proposed package changes and disk usage, then install updates. If another update process holds a lock, wait rather than deleting lock files.

Do not force held-back updates or switch repositories without identifying phased delivery, dependencies, or explicit holds. Cancel an operation that proposes unexpected removal of essential software and inspect repositories and dependencies first.

Check timezone and chrony synchronization

timedatectl
systemctl status chrony --no-pager
chronyc tracking
chronyc sources -v

Timezone controls how time is displayed; synchronization corrects the system clock. To display Korean local time, use sudo timedatectl set-timezone Asia/Seoul and record the previous zone. Servers elsewhere may intentionally retain UTC according to policy.

Inspect the selected time source and synchronization status; retry after the initial boot has settled. If chrony is absent or another daemon runs, identify the installation history before changing services. Changing timezone does not repair an NTP connection or clock error.

Ubuntu’s chrony guide describes default time sources and synchronization checks.

In chronyc sources -v, ^ identifies a server, * the selected source, and + a source combined with it. A ? marks an unusable candidate; investigate reachability, replies, and selection conditions. In tracking, inspect the reference, update time, and Leap status together. Normal does not validate every application’s use of time. Investigate network, DNS, firewall, and time-source availability when unsynchronised or without a selected source.

Set up terminal, editor, and VM tools

Work through the Server VM console or an SSH terminal. Check available editors with command -v nano and command -v vim, then use sudoedit for system files after verifying backups and paths. If an editor is missing, inspect its APT source before installation rather than broadly replacing system tools.

Ubuntu 26.04 changes the providers of sudo and some basic utilities compared with older LTS releases. Check command help and version-specific documentation for option differences rather than replacing core system tools broadly. Install guest-integration tools appropriate to your hypervisor and Ubuntu packages; do not mix products.

Repeat checks after reboot

test -f /run/reboot-required && cat /run/reboot-required
systemctl --failed
uptime

Check reboot requirements and running work before a planned sudo reboot. Sign in again and verify release information, networking, synchronization, and failed services. Record successful package installation separately from functional success after reboot.

Identify sudo and core utility providers on 26.04

Ubuntu 26.04 uses sudo-rs and rust-coreutils in its default toolchain. If an article about GNU-specific options differs from your output, identify the provider and version first. Password-input feedback also depends on implementation and policy. Do not remove or replace all default tools as an unexamined compatibility workaround.

command -v sudo ls cp
sudo --version
ls --version
dpkg-query -W sudo-rs sudo coreutils coreutils-from-uutils coreutils-from-gnu 2>/dev/null

Queries for packages that are not installed may return a nonzero status; this alone is not a system failure. Ubuntu 26.04 release changes