[FAQ Index] | [4.3 -> 4.4] | [4.5 -> 4.6]
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:
Some
ifconfig(8)
options have changed.
To scan for wireless networks, you should now use:
To list supported media types, you should now use:ifconfig interface scan
ifconfig interface media
RgbPath is no longer a valid keyword in the Files
section of the
xorg.conf
file, and should be removed from existing configuration files.
The i810(4) driver has been completely replaced by the intel(4) driver, so your xorg.conf(5) file should be updated accordingly.
Several existing xserver modules and drivers have been depreciated.
To make sure X -configure doesn't try to configure the obsolete
modules, we'll have you remove the contents of /usr/X11R6/lib/modules/
before upgrading.
headphones has been shorted to hp and
speaker was shortened to spkr.
You may need to update your
mixerctl.conf(5)
with the new names.
Who should use sysmerge(8):
People running highly modified systems or systems that didn't start out
at the previous release (for example, a snapshot partway between
releases), who are upgrading to a snapshot or who have not carefully
upgraded their system in the past will find sysmerge vastly superior to
using the patches, as it works with what is actually on your system,
instead of what we expected was on your system.
It will also give you much greater control over your upgrade process,
and will involve you in it more closely.
Who may wish to NOT use sysmerge(8):
People who have a lot of machines to upgrade that were kept fairly
simple and at the previous release/stable point will probably find the
old patch file system much faster.
Note that while sysmerge can handle ALL the changes of /etc,
/dev, /root and /var, we highly recommend
that you do some steps manually before hand, as it will save time and
reduce the possibility of user error.
In particular, it is highly recommended that you do not use sysmerge to
update your user and group accounts, as it is very easy to chose the
wrong option leading to erasing your entire user base and setting the
root password to an empty value, preventing remote login to fix the
problem.
/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.
BEFORE upgrading, however, do the following if you have X installed:
Afterwards, complete the upgrade by following the final steps as detailed below.rm -rf /usr/X11R6/lib/modules/*
One easy way to boot from the install kernel is to place the 4.5 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:
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 /
rm /obsd ;
ln /bsd /obsd && cp bsd.mp /nbsd && mv /nbsd /bsdNote 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.
rm -rf /usr/X11R6/lib/modules/*
cp /sbin/reboot /sbin/oreboot
etc45.tgz and xetc45.tgz now, because
that will overwrite your current configuration files!
Note that we are installing base45.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 now.
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.tar -C / -xzphf xserv45.tgz tar -C / -xzphf xfont45.tgz tar -C / -xzphf xshare45.tgz tar -C / -xzphf xbase45.tgz tar -C / -xzphf game45.tgz tar -C / -xzphf misc45.tgz tar -C / -xzphf comp45.tgz tar -C / -xzphf man45.tgz tar -C / -xzphf base45.tgz # Install last! /sbin/oreboot
Again, the files in /etc are handled separately below, so
etc45.tgz and xetc45.tgz are NOT unpacked here.
/dev.
The new
MAKEDEV
file was copied to /dev by the installation of
base45.tgz, so you simply need to do the following:
cd /dev ./MAKEDEV all
useradd -u94 -g=uid -c"Bluetooth Daemon" -d/var/empty -s/sbin/nologin _btd
/etc
You will want to extract the etc45.tgz files to a temporary
location:
export RELEASEPATH=/usr/rel
tar -C /tmp -xzphf ${RELEASEPATH}/etc45.tgz
etc45.tgz "as is":
Note that it IS possible to locally modify these files, if this has been done, do NOT copy over those files, and use the sysmerge(8) process instead. Here are copy/paste lines for copying these files, assuming you unpackednetstart rc rc.conf services afs/CellServDB mail/README mail/submit.cf mtree/4.4BSD.dist mtree/special /var/named/etc/root.hint /var/named/etc/named*
etc45.tgz in the above recommended place:
cd /tmp/etc cp netstart rc rc.conf services /etc cp afs/CellServDB /etc/afs cp mtree/* /etc/mtree cp mail/README mail/submit.cf /etc/mail cp ../var/named/etc/root.hint ../var/named/etc/named-*.conf /var/named/etc cp ../var/named/etc/named.conf /var/named/etc/ # IF no local changes!
These files likely have local changes, but should be updated for 4.5. IF you have not altered these files, you can copy over the new version, otherwise the changes should be merged with your files:
The changes to these files are in this patch file. You can attempt to use this by executing the following as root:/etc/changelist /etc/ftpusers /etc/ksh.kshrc /etc/lynx.cfg /etc/mail/aliases /etc/mail/trusted-users /etc/shells /etc/ssh/ssh_config
This will test the patch to see how well it will apply to YOUR system; to actually apply it, leave off the "cd / patch -C -p0 < upgrade45.patch
-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 4.4, 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/dhcpd.conf etc/ntpd.conf etc/pf.conf
Finally, use newaliases(8) to update the aliases database, mtree(8) create any new directories:
newaliases mtree -qdef /etc/mtree/4.4BSD.dist -p / -u
The new sysmerge(8) utility will compare the files that are actually on your system with those that would be installed to a fresh install, and assist you in merging the changes into your system. Note that unlike the patch file, 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 -current to 4.5-release or from one -current to a later one.
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.
Assuming the etc45.tgz and xetc45.tgz files exists in
your $RELEASEPATH, run it with:
Sysmerge(8) will show you a unified diff(1), run through your favorite $PAGER (i.e., more(1)) and ask you, for most changed files, if you wish to:# sudo sysmerge -as $RELEASEPATH/etc45.tgz -x $RELEASEPATH/xetc45.tgz
Use '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 hand
If 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.
While it can work, we do not recommend you use sysmerge to integrate new users into the system, but rather use the useradd(8) line above. We believe it is much less error prone. (hint: do not install the temporary master.passwd file over your existing one!).
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.
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.4, it is likely you will need to modify the stock kernel of 4.5. 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 4.5 packages directory on your CD or nearest FTP mirror,
and use something like
where the# pkg_add -ui -F update -F updatedepends
-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.
A number of Perl modules which used to be separate packages are now included with Perl 5.10.0 in the base system, so after updating the other packages, their packages must now be removed. In addition, xcompmgr(1) is now part of xbase45.tgz, and no longer a package, so it must also be removed.
Note that if you copy and paste this command into your system, you will probably get a lot of error messages from packages you don't have installed. That's ok.pkg_delete p5-Archive-Tar p5-Compress-Raw-Zlib p5-Compress-Zlib \ p5-IO-Compress-Base p5-IO-Compress-Zlib p5-IO-Zlib p5-Module-Build \ p5-Module-CoreList p5-Module-Load p5-version p5-Digest-SHA \ p5-Locale-Maketext-Simple p5-Pod-Escapes p5-Pod-Simple \ p5-ExtUtils-ParseXS p5-ExtUtils-CBuilder p5-Module-Pluggable \ p5-Time-Piece p5-Module-Loaded xcompmgr
[FAQ Index] | [4.3 -> 4.4] | [4.5 -> 4.6]