Upgrade Guide: 7.3 to 7.4

[FAQ Index] | [7.2 -> 7.3] [7.4 -> 7.5]

Upgrades are only supported from one release to the release immediately following.
Read through and understand this process before attempting it. For critical or physically remote machines, test it on an identical, local system first.

Before using any upgrade method

Check available disk space in /usr. Verify that the /usr partition has a size of at least 1.1G. With less space the upgrade may fail and you should consider reinstalling the system instead.
Read configuration and syntax changes and the package upgrade instructions. There were several configuration changes and changes in packages that may require planning before starting the upgrade.

Upgrade Methods

Unattended Upgrade: The easiest method is an unattended upgrade using sysupgrade(8). The program will download all the install sets, verify their signatures, and reboot to perform the upgrade automatically. Once the unattended upgrade has completed, continue below.
Interactive Upgrade: If you insist on leaving out some of the install sets, you will want to perform an interactive upgrade. (sysupgrade upgrades with all install sets.)
Manual Upgrade: The final option is using the manual upgrade process. (This is not recommended as it is the most error-prone method.)

Interactive Upgrade

Get and verify bsd.rd. Download the ramdisk kernel and the cryptographically-signed checksum file for your architecture.

bsd.rd

[alpha] [amd64] [arm64] [armv7] [hppa] [i386] [landisk] [luna88k] [macppc] [octeon] [powerpc64] [riscv64] [sparc64]

SHA256.sig

[alpha] [amd64] [arm64] [armv7] [hppa] [i386] [landisk] [luna88k] [macppc] [octeon] [powerpc64] [riscv64] [sparc64]

Verify bsd.rd and SHA256.sig using signify(1):
```
$ signify -C -p /etc/signify/openbsd-74-base.pub -x SHA256.sig bsd.rd
Signature Verified
bsd.rd: OK
```
Next, boot from the install kernel, bsd.rd, retrieved in the previous step. Place it in the root of your filesystem and instruct the boot loader to boot this kernel. Once this kernel is booted, choose the (U)pgrade option and follow the prompts.
After the filesets have been installed, the system will reboot with the upgraded kernel. Now continue with the next step:

After the Upgrade

After upgrading the sets, the system will reboot with the upgraded kernel and run sysmerge(8) during boot. In some cases, configuration files cannot be modified automatically. Run

 # sysmerge

to check and perform these configuration changes.

Next remove the old files. Finish up by upgrading the packages using pkg_add -u.

You may wish to check the errata page for any post-release fixes.

Manual Upgrade (without the install kernel)

This is NOT the recommended process. Use the unattended or interactive upgrade methods if at all possible!

Sometimes, you need to perform an upgrade of a machine for which the normal unattended or interactive upgrade process is not possible.

Preparation

Place install files in a good location. Make sure you have sufficient space! Running out of space on a remote upgrade could be...unfortunate. Note that using softdeps can exacerbate the situation as deleted and overwritten files do not release their space immediately. Consider disabling the softdep mount option in /etc/fstab and rebooting before undertaking a manual upgrade. Having at least 500MB free on /usr would be recommended.
Become root. While using doas(1) before each command is generally a good practice, the command will likely be broken by the last steps, so you should become root before starting this process. It might be good to verify your access to root using a method other than doas at this point, i.e., direct login or using su(1).
Stop and/or disable any appropriate applications. During this process, all the userland applications will be replaced but may not be runnable, and strange things may happen as a result. You may also have issues with DNS resolution during the first reboot, so PF rules and NFS mounts dependent upon DNS may cause boot-up problems. There may be other applications which you wish to keep from running immediately after the upgrade; stop and disable them as well.
Install new boot blocks. This should actually be done at the end of any upgrade. If this has been neglected, then failure to do this now may break serial console or other things, depending on your platform. Use installboot(8), assuming sd0 is your boot disk:
```
# installboot sd0
```

Upgrading manually

Install new kernels. The extra steps for copying over the primary kernel are done to ensure that there is always a valid kernel on the disk.

If using the multiprocessor kernel:

# cd /usr/rel    # where you put the release files
# ln -f /bsd /obsd && cp bsd.mp /nbsd && mv /nbsd /bsd
# cp bsd.rd /
# cp bsd /bsd.sp

If using the single processor kernel:

# cd /usr/rel    # where you put the release files
# ln -f /bsd /obsd && cp bsd /nbsd && mv /nbsd /bsd
# cp bsd.rd bsd.mp /    # may give a harmless warning

Enable KARL. Store the kernel's checksum:
```
# sha256 -h /var/db/kernel.SHA256 /bsd 
```

Install new userland. Save a copy of reboot(8), extract and install the release tarballs, reboot. Install base74.tgz last, because the new base system, in particular tar(1), gzip(1) and reboot(8), will not work with the old kernel. Either untar the needed filesets manually:

# cp /sbin/reboot /sbin/oreboot
# tar -C / -xzphf xshare74.tgz
# tar -C / -xzphf xserv74.tgz
# tar -C / -xzphf xfont74.tgz
# tar -C / -xzphf xbase74.tgz
# tar -C / -xzphf man74.tgz
# tar -C / -xzphf game74.tgz
# tar -C / -xzphf comp74.tgz
# tar -C / -xzphf base74.tgz    # Install last!
# /sbin/oreboot

or, if you use ksh(1), you can do:

# cp /sbin/reboot /sbin/oreboot
# for _f in [!b]*74.tgz base74.tgz; do tar -C / -xzphf "$_f" || break; done
# /sbin/oreboot

Note that tar(1) can expand only one archive per invocation, so a simple glob won't work.

After reboot, update /dev. Run MAKEDEV(8):
```
# cd /dev
# ./MAKEDEV all
```
Update the boot loader. Still assuming sd0 is your boot disk:
```
# installboot sd0
```
Update system configuration files. Run sysmerge(8):
```
# sysmerge
```
Update firmware. There may be new firmware for your system. Update it with fw_update(8):
```
# fw_update
```
Finish up. Review the console output from boot (using dmesg -s) and correct any failures as necessary. All the steps following configuration changes below also apply to manual upgrades. Finally, remove /sbin/oreboot and update packages: pkg_add -u. Reboot once more to make sure you use the newest firmware files and run on your own kernel generated by KARL.

Configuration and syntax changes

bioctl(8). bioctl(8) now defaults to a system performance based number of KDF iterations for passphrases.
Update the passphrase on existing CRYPTO and RAID 1C softraid(4) volumes to update the number of rounds to a new hardware based default:
```
  # bioctl -v -P sd1
```
pfsync(4). pfsync(4) has been rewritten. In most cases, no change is needed and the protocol is compatible with the older version.
However, if you configured it with a hostname.pfsyncX entry like:
```
  up
  syncdev $interface
```
Then it will need to be rearranged so the interface is configured before being brought up:
```
  syncdev $interface
  up
```
shutdown(8). shutdown(8) has changed from group operator to group _shutdown to separate the ability to use shutdown from other privileges operator grants.
Those users who were given group operator should be moved to _shutdown in order to continue using shutdown(8).

Files to remove

Nothing to remove this release

Special packages

borgbackup 1.1.x. borgbackup 1.1.x. is end-of-life and has been removed. A package upgrade will install a 1.2.x version.
Before upgrading it is recommended to follow the borgbackup upgrade notes.
borgbackup 1.2.x. A flaw in the cryptographic authentication scheme in borgbackup versions before 1.2.5 allowed an attacker to fake archives and potentially indirectly cause backup data loss in the repository. borgbackup versions 1.2.5 and later enforces checking the TAM authentication tag of archives at critical places, and now considers archives without TAM as garbage or an attack.
Steps you must take to upgrade a repository are detailed in the borgbackup documentation.
exim. Exim's internal SPF support has been disabled due to an integer underflow vulnerability in the library used for SPF processing. If using SPF checks directly in Exim you'll need to disable that part of configuration (you may be able to replace this with checks in spam filtering software; at least rspamd and spamassassin can do SPF checks).
Additionally, exim's AUTH_SPA (NTLM) support has been disabled in the port, to match upstream's default.
influxdb. Influxdb has been upgraded to a new major version, which has several impacts:
The influx command line interface is now in the separate influx-cli package, and has a completely different syntax.
Authentication is now mandatory via token, and the db is multi-tenant so an organization is also mandatory.
The web interface is now built-in and accessible on port 8086 by default. The database format needs to be upgraded with:
```
  # doas -u _influx influxd upgrade
```
(Also see the upstream documentation)
nextcloud 23. Nextcloud 23 must be updated before upgrading.
Nextcloud 23 and 24 have been removed. As Nextcloud upgrades are only supported from one major version to the next, users of Nextcloud 23 must update to at least Nextcloud 24 before upgrading OpenBSD otherwise they will not be able to follow upstream's supported process. To do this, first backup your configuration and database, then pkg_delete nextcloud and pkg_add nextcloud selecting a 24.x release before following the usual Nextcloud upgrade procedure via the web interface or occ upgrade.

telegraf. Telegraf clients will need to be updated to use the outputs.influxdb_v2 plugin (with org, token and bucket) per the documentation

There is no more collectd direct sink in influxdb. collectd now needs to talk to telegraf with a collectd-enabled sink. An example configuration for telegraf.conf is provided below:

  [[inputs.socket_listener]]
    service_address = "udp://:25826"
    data_format = "collectd"
    collectd_auth_file = "/etc/collectd/collectd.auth"
    collectd_security_level = "encrypt"
    collectd_typesdb = ["/usr/local/share/collectd_types.db"]
    collectd_parse_multivalue = "split"
  [[outputs.influxdb_v2]]
   urls = ["http://influxdb:8086"]
   token = "$DOCKER_INFLUXDB_INIT_ADMIN_TOKEN"
   organization = "$DOCKER_INFLUXDB_INIT_ORG"
   bucket = "$DOCKER_INFLUXDB_INIT_BUCKET"

tor browser. Tor Browser has been updated to 12.5.3.
As of the 12.5 release, torrc has been moved from ~/TorBrowser-Data/torrc to ~/TorBrowser-Data/Tor/torrc. If you wish to preserve your tor configuration (e.g., bridges), please do the following BEFORE starting tor-browser after you upgrade:
```
  $ mv ~/TorBrowser-Data/torrc ~/TorBrowser-Data/Tor/
```

[FAQ Index] | [7.2 -> 7.3] [7.4 -> 7.5]

$OpenBSD: upgrade74.html,v 1.6 2024/05/02 19:32:53 sthen Exp $