FreeBSD Fundamentals · Module 13 of 14

Updates, upgrades and lifecycle hardening

Maintain the FreeBSD base system and third-party packages with release-aware procedures and explicit rollback planning.

Learning objectives

By the end of this module, you should be able to:

Distinguish updating from upgrading.
Apply base-system and package maintenance with release-aware tooling.
Audit security posture before and after maintenance.

Base and package lifecycles

Traditional RELEASE installations use freebsd-update for binary base-system security/errata updates and supported upgrades. FreeBSD 15 also introduces pkgbase as a tech-preview path, so administrators must know how the host was installed before choosing lifecycle commands.

Major upgrades change ABI expectations

After a major FreeBSD upgrade, third-party packages may need forced replacement/reinstallation because the ABI changed. Read the target release notes and Handbook procedure rather than improvising.

Worked examples

See the idea in practice.

Inspect before maintenance

freebsd-version -ku
pkg -vv | grep -E "ABI|url" | head
pkg audit -F || true

Identify release and package-repository context before changing anything.

Hands-on lab

Lab — Build an update readiness report

Goal: Collect the facts needed for a safe maintenance plan without performing an upgrade.

Before you start

Internet access; do not perform a major upgrade in this lab.

STEP 1

Record release

freebsd-version -ku
uname -a

STEP 2

Check package health

pkg audit -F || true
pkg upgrade -n

STEP 3

Check base update method

test -x /usr/sbin/freebsd-update && echo freebsd-update-present
pkg -vv | grep -i FreeBSD-base || true

Verify

You can state the installed release, package changes pending and likely base-update method.

Expected outcome

No major upgrade occurs; this is a readiness exercise.

If it fails

If your host uses pkgbase, follow the current Handbook for that release rather than applying traditional freebsd-update steps blindly.

Real-world connection

Lifecycle safety starts with knowing the installation/update model of the host.

Avoid these traps

Common mistakes

Mixing pkgbase and traditional update instructions without identifying the host model.
Performing a major upgrade without backups/rollback and release notes.

Knowledge check

Can you explain it without looking back?

Open each answer only after you have tried to answer the question yourself.

1What is an update versus an upgrade in FreeBSD terminology?

An update applies security/errata within a release; an upgrade moves to a different release version.

2Why identify pkgbase first?

FreeBSD 15 can use a different base-system lifecycle path, so the correct maintenance procedure depends on how the host is managed.

3What should accompany a major upgrade?

Backups or boot-environment rollback, release-note review, package planning and console/recovery access.

My Learning

Record your progress for this module.

Progress is saved in this browser immediately. When you sign in to My Learning, it can also sync across devices.

Not started

Core lab attemptedRecord this after meaningfully completing or attempting the module's core lab.Knowledge checks attemptedThis is marked automatically after you open every answer in the module; you can also record it manually.

Attempt the core lab and knowledge checks before marking the module complete.