OpenBSD Upgrade Guide: 3.9 to 4.0

[FAQ Index] | [3.8 -> 3.9] | [4.0 -> 4.1]

Note: Upgrades are only supported from one release to the release immediately following it. Do not skip releases.

It is highly recommended that you read through and fully understand this process before attempting it. If you are doing it on a critical or physically remote machine, it is recommended that you test this process on an identical, local system to verify its success before attempting on a critical or remote computer.

Upgrading is a convenient way to bring your OpenBSD system up to the most recent version. However, the results are not intended to precisely match the results of a wipe-and-reload installation. Old library files in particular are not removed in the upgrade process, as they may be required by older applications that may or may not be upgraded at this time. If you REALLY wish to get rid of all these old files, you are probably better off reinstalling from scratch.

Table of Contents:

Before upgrading

Check whether you have made any modifications to your kernel. For example, you might have modified your network device to use a non-default setting using config(8). Note your changes, so you can repeat them for the new 4.0 kernel.

The upgrade process

Upgrading by install media

The easiest and safest way to upgrade is to boot from install media and follow the upgrade steps, which are very similar to the install process. Afterwards, complete the upgrade by following the final steps as detailed below.

Upgrading without install media

This is NOT the recommended process. Use the install media method if at all possible!

Sometimes, one needs to do an upgrade of a machine when one can't easily use the normal upgrade process. One can usually do this by carefully following a process similar to building the system from source:

During this process, sendmail(8) may produce some error messages like the following:
    Nov 1 12:47:05 puffy sm-mta[16733]: filesys_update failed: No such file or directory, fs=., avail=-1, blocksize=380204
These messages can be safely ignored, or you may wish to halt sendmail(8) during the upgrade process.

Final steps

1. Upgrading /etc

Whether you upgrade by using an install media and doing a formal "upgrade" process, or do a "in-place" binary upgrade, there are certain manual steps that have to be performed.

1.1. New users and groups

1.2. Operational changes

1.3. /etc file changes

You will want to extract the etc40.tgz files to a temporary location:
cd /tmp
tar xzpf ${RELEASEPATH}/etc40.tgz
Files that can probably be copied from etc40.tgz "as is":
Note that it IS possible to locally modify these files, if this has been done, manual merging will be needed. Pay special attention to mail/ if you are using something other than the default Sendmail(8) configuration. Here are copy/paste lines for copying these files, assuming you unpacked etc40.tgz in the above recommended place:
cd /tmp/etc
cp chio.conf dvmrpd.conf netstart pf.os rc security services /etc
cp mail/helpfile mail/ mail/ /etc/mail
cp ppp/ppp.conf.sample /etc/ppp
cp mtree/* /etc/mtree/
cp mail/ /etc/mail    # careful on this one!!
A couple pages for httpd(8)'s documentation changed:
This can be copied (if desired) by:
cd /tmp/var/www/htdocs/manual/mod/
cp core.html mod_proxy.html /var/www/htdocs/manual/mod

Files that must be manually merged, respecting any local changes made to them, if they were modified from the default, otherwise, just copy them over, too:

The changes to these files are in this patch file. You can attempt to use this by executing the following as root:
cd /
patch -C -p0 < upgrade40.patch
This will test the patch to see how well it will apply to YOUR system, to actually apply it, leave off the "-C" option. Note that it is likely that if you have customized files or not kept them closely updated, or are upgrading from a snapshot of 3.9, they may not accept the patch cleanly. In those cases, you will need to manually apply the changes. Please test this process before relying on it for a machine you can not easily get to.

The following files have had changes which should be looked at, but it is unlikely they should be directly copied or merged (i.e., if you are using pf.conf, look at the suggested change of strategy, and decide if it is appropriate for your use).


Finally, use mtree(8) to create any new directories:
mtree -qdef /etc/mtree/4.4BSD.dist -p / -u

2. Checking the kernel

Note: most people can skip this step!

If you followed the instructions for the upgrade process without install media, you have already completed this step. However, if you used the install media, and if you had a modified kernel in 3.9, it is likely you will need to modify the stock kernel of 4.0. This can be as simple as modifying a specific device using config(8), or it can involve a recompilation if the option you need is not included in the GENERIC kernel. Please consult FAQ 5 - Building the system from source before considering to recompile your kernel.

3. Upgrading packages

If you installed any packages on your system, you may want to upgrade them after completing the upgrade of the base system. The package tools support in-place updating using pkg_add -u. For instance, to update all your packages, make sure PKG_PATH is pointing to the 4.0 packages directory on your CD or nearest FTP mirror, and use something like
# pkg_add -ui -F update -F updatedepends
where the -u indicates update mode, and -i specifies interactive mode, so pkg_add will prompt you for input when it encounters some ambiguity. Read the pkg_add(1) manual page and the package management chapter of the FAQ for more information.

[FAQ Index] | [3.8 -> 3.9] | [4.0 -> 4.1]

$OpenBSD: upgrade40.html,v 1.24 2019/05/28 01:53:11 bentley Exp $