Before you touch a disk
Welcome to the BSD side of the terminal. This walkthrough installs FreeBSD 15.1-RELEASE on a standard 64-bit Intel/AMD computer using the text-based bsdinstall installer. FreeBSD 15.1 was released on 16 June 2026. Screens and options may change with later releases.
Safest first attempt: a spare computer, an empty SSD, or a virtual machine. If you have Windows and Slackware already installed, leave that disk alone. Dual-boot partitioning requires a separate, careful plan; this tutorial intentionally does not teach repartitioning a working Windows/Linux disk.
Any installation can erase data. Back up the files that matter to a different physical device, confirm the backup opens, and make sure you can identify the correct target disk by its size and model. “Entire Disk” and automatic ZFS installation erase the selected disk.
What you need
- A 64-bit Intel/AMD PC (
amd64) or an appropriately configured virtual machine. - A spare USB flash drive (8 GB or larger is convenient), if installing on real hardware.
- A keyboard and monitor. A wired Ethernet connection is easiest for a first installation.
- Enough free space on the target disk and a separate backup of anything important.
1 · Download the official installer
Go to Get FreeBSD. In the FreeBSD 15.1-RELEASE section, choose amd64 for a typical modern Intel/AMD PC. For a USB stick, choose the memstick image (typically named FreeBSD-15.1-RELEASE-amd64-memstick.img.xz). For a virtual machine, an installer ISO may be more convenient.
Download the official matching SHA256 checksum file and compare it against the compressed file before writing a USB. Verify the hash of the exact file you downloaded, not an example from somebody else's tutorial.
On Slackware or another Linux system, run:
sha256sum FreeBSD-15.1-RELEASE-amd64-memstick.img.xz
On Windows PowerShell, use:
Get-FileHash .\FreeBSD-15.1-RELEASE-amd64-memstick.img.xz -Algorithm SHA256
The digest must match the value in the official checksum file for that exact download. If the filename differs, use the filename you actually downloaded.
2 · Create installation media
On Windows, use a reputable image-writing utility that supports raw disk images. On Linux, a graphical image writer is a sensible option. USB creation overwrites the flash drive, so choose its device carefully.
Experienced Linux users can write an uncompressed .img using dd. This example is intentionally separated from the beginner path because choosing the wrong of= device can wipe an internal drive.
Do not copy the sample disk path without identifying your USB first. Use lsblk -o NAME,SIZE,MODEL,TRAN and confirm model, size and the whole USB device (not a partition). Unplug other removable disks if practical.
Example for experienced Linux users only (replace /dev/sdX with your verified USB device):
xz -dk FreeBSD-15.1-RELEASE-amd64-memstick.img.xz
lsblk -o NAME,SIZE,MODEL,TRAN
# STOP: verify your USB device before running the following line.
sudo dd if=FreeBSD-15.1-RELEASE-amd64-memstick.img of=/dev/sdX bs=4M status=progress conv=fsync
Let the writer finish completely before removing the stick. On a VM, attach the ISO in the VM's virtual optical drive instead; no USB is needed.
3 · Boot into the FreeBSD installer
- Insert the USB, start the spare computer, and open its firmware boot menu (often F12, F11 or Esc, depending on the model).
- Choose the USB's UEFI boot entry if the machine uses UEFI. A VM should boot its attached installer ISO.
- At the FreeBSD boot menu, accept the normal boot option.
- In
bsdinstall, choose Install. Follow the keyboard map prompt; the default layout is fine if it matches your keyboard. - Set a hostname such as
freebsd-lab(or a host name appropriate for your own network).
These are text menus, not a command prompt. Use arrows to move, Space to toggle options, and Enter to confirm.
4 · Choose a base-system installation method
FreeBSD 15.x has an important new choice. For an ordinary learning machine, we recommend Distribution Sets: the classic installer method. The alternative Packages (Tech Preview) is for testing the newer pkgbase method.
| Choice | What it means | Our suggestion |
|---|---|---|
| Distribution Sets | Traditional base-system install; base OS updated with freebsd-update. | Choose this for your first install. |
| Packages (Tech Preview) | Base OS installed and maintained as packages via pkg. | Experiment with this later, preferably in a VM. |
Both methods can install third-party software with pkg. The difference matters when updating the operating system itself, which we cover below.
5 · Partitioning: UFS or ZFS
The installer can offer Auto (UFS), Auto (ZFS), Manual, and Shell choices. The exact options vary by hardware and installer version.
| Option | Good for | Risk to remember |
|---|---|---|
| Auto (UFS) | Simple first installation and modest lab machines. | “Entire Disk” overwrites the selected disk; partition choices still need careful review. |
| Auto (ZFS) | Experimenting with ZFS features and storage management. | The guided root-on-ZFS method works on whole disks and erases the chosen disk. |
| Manual / Shell | Advanced partition layouts and knowledgeable dual-boot users. | Not covered here; errors can damage other operating systems. |
DarkPC starter recommendation: pick Auto (UFS) on a known empty dedicated disk. A small ZFS practice machine is also great, but read the ZFS requirements and make sure you are using the intended whole disk. For a modern UEFI amd64 machine, GPT is normally the appropriate partition table.
When the installer shows a disk such as ada0, da0 or nvd0, verify its model and size against the device you set aside. If you cannot tell which disk is which, cancel rather than guess. Disk names are not permanent promises.
Confirm the proposed changes only when you are certain the selected disk may be erased. Let bsdinstall install the base system.
6 · Network, accounts, time and services
- If prompted, configure wired Ethernet with DHCP for the first install. Wireless support varies by adapter; don't assume your Linux Wi-Fi driver works in FreeBSD.
- Choose your correct time zone (for example, Australia/Sydney when appropriate).
- Set a strong, unique root password and store it securely.
- Create your own non-root user. If you want that user to be able to use
su, add the user to thewheelgroup in the installer. - Review any suggested optional services and security settings. Enable SSHD only if you actually need remote access and know how to secure it.
- When installation finishes, remove the installer USB when prompted and Reboot.
Log in as the normal user you created. Your screen should greet you with a good old-fashioned shell prompt. No heavyweight desktop required.
7 · Your first five minutes at the prompt
First, check that you are running the expected release and can see the installed filesystems:
whoami
uname -a
freebsd-version
pwd
df -h
Now test your network and DNS:
ifconfig
netstat -rn
ping -c 4 freebsd.org
freebsd-version shows the installed FreeBSD version. ifconfig displays network interfaces; netstat -rn shows the routing table. If the ping fails, fix networking before trying to install extra software.
8 · Install your first terminal applications
On a normal FreeBSD install, the system package manager is pkg. The first invocation may ask permission to bootstrap the actual package manager. Switch to a root shell for software installation:
su -
pkg update
pkg search tmux
pkg install tmux irssi neomutt links
exit
The available package names and versions can change; always read the install plan before you confirm. Now, as your normal user:
tmux -V
command -v irssi
command -v neomutt
command -v links
You're now very close to a DarkPC-style FreeBSD workstation: IRC, email, a text browser and a multiplexer, with no full desktop environment required.
9 · Update FreeBSD the right way
Don't confuse updating third-party packages with updating the FreeBSD base operating system. Which base method you selected in step 4 determines the correct approach.
For a typical Distribution Sets installation, run as root:
su -
freebsd-update fetch
freebsd-update install
pkg update
pkg upgrade
exit
Read every message, and reboot when the OS update advises it. pkg update refreshes package catalogue information; pkg upgrade updates installed packages. With the classic distribution-set method, pkg upgrade does not replace freebsd-update for base system updates.
If you instead chose Packages (Tech Preview), do not blindly follow the above freebsd-update sequence. The pkgbase workflow uses pkg for the base system. Follow the official FreeBSD updating chapter for your exact setup.
10 · When something doesn't work
| Problem | First check |
|---|---|
| The installer will not boot | Check architecture, image type, UEFI boot selection, and that the USB image was fully written. |
| No network after first boot | Try wired Ethernet, run ifconfig, confirm your router provides DHCP; consult driver/hardware notes. |
| No DNS but an IP address works | Check /etc/resolv.conf and network configuration; don’t replace DNS settings blindly. |
pkg cannot reach repositories | Verify ping -c 4 freebsd.org, routing, correct date/time, and repository connectivity. |
su says permission denied | Ensure the user is in wheel and that you are using the root password; do not log in as root for everyday work. |
| Your old OS disappeared | Stop writing to that disk. Avoid experimenting with further partition commands; restore from backups or seek expert help. |
A good next step is the FreeBSD Terminal Survival Guide for the commands you'll actually use, including finding files, packages, services, logs and networking.
Official references
- FreeBSD: official downloads and supported releases
- FreeBSD Handbook: Installing FreeBSD
- FreeBSD Handbook: Packages and Ports
- FreeBSD Handbook: Updating and Upgrading
- FreeBSD 15.1 release notes
DarkPC guide reviewed 16 October 2026. Official documentation takes precedence if the installer or update procedure changes.