[FAQ Index] | [5.1 -> 5.2] | [5.3 -> 5.4]
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:
/etc
and /var
.
We now believe that
sysmerge(8)
is a much better and more accurate tool for most users.
For this reason, we will no longer be providing a updateXX.patch file
as part of these upgrade instructions.
xorg.conf
file.
To force the use of the
radeonold(4)
driver, add the following to /etc/X11/xorg.conf
:
Section "Device" Identifier "Old Radeon Card" Driver "radeonold" EndSection
"all"
keyword
becomes "any"
.
You need to update your config. Be careful to really rewrite rules like:
accept from all [...]to
accept from any [...]because the former syntax is still valid, but it behaves completely differently now and it would break your rule set.
set queue
" instead of just
"queue
":
The new syntax is documented in
pf.conf(5)
bysndiod -frsnd/1 -r44100
MIDI thru boxes are created dynamically so -M options must be removed. MIDI ports (-q) cannot be connected to the sndiod control port, so an external program must be used for that (eg. aucat(1) or the audio/midish port). For instance, to make rmidi/5 control snd/0 do:sndiod -r44100 -frsnd/1
aucat -M -mmidi -qrmidi/5 -qsnd/0
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 5.3 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.
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:
(note: you will get a harmless error message if your platform doesn't have a bsd.mp):export RELEASEPATH=/usr/rel # where you put the files cd ${RELEASEPATH} rm /obsd ; ln /bsd /obsd && cp bsd /nbsd && mv /nbsd /bsd cp bsd.rd bsd.mp /
export RELEASEPATH=/usr/rel # where you put the files cd ${RELEASEPATH} rm /obsd ; ln /bsd /obsd && cp bsd.mp /nbsd && mv /nbsd /bsd cp bsd.rd / cp bsd /bsd.sp
Note the extra steps for copying over the primary kernel: those are done to ensure that there is always a valid copy of the kernel on the disk that the system can boot from should there be a really badly timed power outage or system crash.
etc53.tgz
and xetc53.tgz
now, because
that will overwrite your current configuration files!
Note that we are installing base53.tgz LAST, because it will include a new
tar(1)
utility, which may or may not run on the old kernel.
We reboot immediately, as the system is probably barely runnable after
the unpacking of all the new files.
Not all file sets will need to be installed for all applications, however if you installed a file set originally, you should certainly upgrade it with the new file set now.cp /sbin/reboot /sbin/oreboot tar -C / -xzphf xserv53.tgz tar -C / -xzphf xfont53.tgz tar -C / -xzphf xshare53.tgz tar -C / -xzphf xbase53.tgz tar -C / -xzphf game53.tgz tar -C / -xzphf comp53.tgz tar -C / -xzphf man53.tgz tar -C / -xzphf base53.tgz # Install last! /sbin/oreboot
Again, the files in /etc
are handled separately below, so
etc53.tgz
and xetc53.tgz
are NOT unpacked here.
/dev
.
The new
MAKEDEV
file was copied to /dev by the installation of
base53.tgz
, so you simply need to do the following:
cd /dev ./MAKEDEV all
The sysmerge(8) utility will compare the files that are actually on your system with those that would be installed in a fresh install, and assist you in merging the changes into your system. There are no assumptions made about what is actually on your system, so you can use sysmerge(8) to move between more arbitrary points in the development process, such as from an earlier 5.2-current to 5.3-release or from one -current to a later one. Sysmerge(8) compares the current files on your system with the files that would have been installed with a new install, and what would have been there from the last run of sysmerge. Usually, it can figure out what to do to update your files, but if it has difficulty, it will give you the option of keeping the old file, installing the new file, or assisting you in the manual merging of the old and new files, using sdiff.
Please read the sysmerge(8) manual page before using it on your system. You are also advised to read the diff(1), sdiff(1) and even review more(1) manual pages before continuing. A wide terminal window (i.e., significantly more than 80 characters), if available, will make sdiff(1) easier to use.
Assuming the
etc53.tgz
andxetc53.tgz
files exists in your ${RELEASEPATH}, run it with:For the files sysmerge(8) can't resolve on its own, it will show you a unified diff(1), run through your favorite $PAGER (i.e., more(1)) and ask you if you wish to:sysmerge -s ${RELEASEPATH}/etc53.tgz -x ${RELEASEPATH}/xetc53.tgzUse 'd' to delete the temporary ./var/www/htdocs/index.html Use 'i' to install the temporary ./var/www/htdocs/index.html Use 'm' to merge the temporary and installed versions Use 'v' to view the diff results again Default is to leave the temporary file to deal with by handIf you wish to retain your existing file, delete the temporary file, if you wish to replace your existing file with the new version, install the temporary file. If you wish to merge the two together, choosing 'm' will put you into sdiff(1), where you can manually merge the file. The default is to come back and deal with the file later, manually.
Sysmerge(8) saves all your replaced files into a temporary directory, similar to
/var/tmp/sysmerge.24959/backups
, so if you accidentally clobber something that was probably not such a good idea, you have a chance to recover it. Note that daily(8) cleans old files from this directory, but it will survive a reboot.
rm /usr/bin/pmdb /usr/share/man/man1/pmdb.1 rm -rf /usr/X11R6/lib/X11/config rm -f /usr/X11R6/bin/{ccmakedep,cleanlinks,imake,makeg,mergelib,mkdirhier,mkhtmlindex,revpath,xmkmf} rm -f /usr/X11R6/man/man1/{ccmakedep,cleanlinks,imake,makeg,mergelib,mkdirhier,mkhtmlindex,revpath,xmkmf}.1 rm -r /usr/lib/gcc-lib/*-unknown-openbsd5.2
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 5.2, it is likely you will need to modify the stock kernel of 5.3. 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.
The following packages are 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 5.3 packages directory on your CD or nearest FTP mirror,
and use something like
where thepkg_add -u
-u
indicates update mode;
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] | [5.1 -> 5.2] | [5.3 -> 5.4]