[OpenBSD]

[3.4 -> 3.5] | [3.5 -> 3.6] | [3.6 -> 3.7] | [3.7 -> 3.8] | [3.8 -> 3.9] | [3.9 -> 4.0] | [4.1 -> 4.2] | [FAQ Index]

Upgrade Guide: 4.0 to 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.1 kernel.

rc.conf: Unlike previous versions of this process, it is now assumed that /etc/rc.conf is not a user-altered file. If you have made changes to your /etc/rc.conf file, merge those changes into /etc/rc.conf.local. If you have NO /etc/rc.conf.local, simply copy your existing /etc/rc.conf file to /etc/rc.conf.local and delete the last line of the script! Otherwise, pull your existing rc.conf into the top of your existing rc.conf.local file and remove the last line before doing the rest of this process.

Special note for ARM users (armish, zaurus): Changes in the ABI requires a slightly different upgrade process if not using standard install kernel. Do not reboot after installing the kernel and before installing the new userland.


The upgrade process

Upgrading by install kernel

If you have access to the system's console, the easiest and safest way to upgrade is to boot from install media or bsd.rd 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.

One easy way to boot from the install kernel is to place the 4.1 version of bsd.rd in the root of your boot drive, then instruct the boot loader to boot using this new bsd.rd file. On amd64 and i386, you do this by entering "boot bsd.rd" at the initial boot> prompt.

Upgrading without install kernel

This is NOT the recommended process. Use the install kernel 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. The most common case is when the machine is in a remote location and you don't have easy access to the system console. One can usually do this by carefully following this process:

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 dire ctory, 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 kernel 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

This is not a complete list of the changes that took place between 4.0 and 4.1, but rather some of the important things that will impact a large number of users in the upgrade process. For a more complete list of changes, see plus41.html and the CVS change logs.

1.3. /etc file changes

You will want to extract the etc41.tgz files to a temporary location:
tar -C /tmp -xzpf ${RELEASEPATH}/etc41.tgz
Files that can probably be copied from etc41.tgz "as is":
etc/daily etc/disktab etc/hoststated.conf etc/magic etc/monthly etc/netstart etc/rc etc/rc.conf etc/ripd.conf etc/sasyncd.conf etc/security etc/weekly etc/mail/Makefile etc/mail/localhost.cf etc/mail/sendmail.cf etc/mail/submit.cf etc/mail/spamd.conf etc/mtree/* var/www/conf/bgplg.css var/www/conf/bgplg.foot var/www/conf/bgplg.head var/www/htdocs/bgplg/*
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 etc41.tgz in the above recommended place:
cd /tmp/etc cp daily disktab hoststated.conf magic monthly netstart rc rc.conf ripd.conf sasyncd.conf security weekly /etc cp mtree/* /etc/mtree/ cp mail/Makefile mail/localhost.cf mail/submit.cf /etc/mail cp mail/sendmail.cf /etc/mail # Careful on this one!! cp mail/spamd.conf /etc/mail # OR... mv /etc/spamd.conf /etc/mail cd /tmp/var/www cp conf/bgplg.css conf/bgplg.foot conf/bgplg.head /var/www/conf mkdir /var/www/htdocs/bgplg cp htdocs/bgplg/* /var/www/htdocs/bgplg/

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:

etc/changelist etc/ftpusers etc/login.conf etc/newsyslog.conf etc/services etc/sysctl.conf etc/mail/aliases var/cron/tabs/root
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 < upgrade41.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).

etc/hostapd.conf etc/pf.conf etc/sensorsd.conf
Finally, use newaliases(8) to update the aliases database and mtree(8) to create any new directories:
newaliases 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 kernel, you have already completed this step. However, if you used the install kernel, and if you had a modified kernel in 4.0, it is likely you will need to modify the stock kernel of 4.1. 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 should upgrade them after completing the upgrade of the base system. Be aware, however, many packages will require further setup before and/or after upgrading the package. Check with the application's upgrade guide for details.

The following package is known to have significant upgrade issues that will impact a large number of users. The fact that a package is not on this list doesn't mean it will have a trivial upgrade. You must do some homework on the applications YOU use.

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.1 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.

[3.4 -> 3.5] | [3.5 -> 3.6] | [3.6 -> 3.7] | [3.7 -> 3.8] | [3.8 -> 3.9] | [3.9 -> 4.0] | [4.1 -> 4.2] | [FAQ Index]


[back] www@openbsd.org
$OpenBSD: upgrade41.html,v 1.29 2007/11/01 02:17:10 nick Exp $