FreeBSD Fundamentals · Module 01 of 14

FreeBSD and the Unix systems model

Understand FreeBSD as an integrated operating system, distinguish the base system from third-party packages, and navigate its documentation culture.

Learning objectives

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

  • Explain the integrated FreeBSD base-system model.
  • Locate authoritative help with man pages and the Handbook.
  • Compare FreeBSD and Linux without assuming command-for-command equivalence.

Base system and third-party software

FreeBSD develops the kernel and a coherent userland as one base operating system. Third-party applications are installed separately, most commonly with pkg or through the Ports Collection.

This distinction matters operationally: base-system lifecycle and third-party package lifecycle are related but not identical.

  • Base system: kernel, core userland, system libraries and administration tools.
  • Packages/ports: additional third-party applications.

Documentation is part of the operating model

FreeBSD manual pages are a primary reference for commands, configuration files, libraries and kernel interfaces. The Handbook provides task-oriented administration guidance.

Worked examples

See the idea in practice.

Identify the running system

uname -a
freebsd-version -ku
which sh
man hier
  • freebsd-version reports installed userland/kernel version information.
  • man hier explains the filesystem hierarchy.
Hands-on lab

Lab — Orient yourself on a FreeBSD host

Goal: Identify the release, base-system tools, filesystem hierarchy and documentation entry points.

Before you start

  • A FreeBSD VM or host with shell access.
STEP 1

Record release and kernel

uname -a
freebsd-version -ku
STEP 2

Explore the hierarchy

man hier
ls -ld / /etc /usr /usr/local /var
STEP 3

Compare base and local software

which service pkg
pkg -vv | head -20

Verify

  • You can identify the release and locate /usr/local for third-party software.

Expected outcome

  • Commands return version and hierarchy information without changing the system.

If it fails

  • If pkg is not bootstrapped, run pkg only when you intentionally want to initialize package management.
Real-world connection

FreeBSD operations become easier when you know which subsystem owns a file or command.

Avoid these traps

Common mistakes

  • Treating FreeBSD as simply another Linux distribution.
  • Editing configuration before checking the relevant man page.
Knowledge check

Can you explain it without looking back?

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

1What is the base system?

The kernel and core userland maintained as an integrated FreeBSD operating system.

2Where are third-party configuration files commonly placed?

Under /usr/local/etc rather than mixing them into the base-system /etc namespace.

3Why use man pages during operations?

They document the exact command or configuration interface shipped with the system.

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

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