![[OpenBSD]](../images/smalltitle.gif){kind=small}
[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.0 -> 4.1] |
[4.1 -> 4.2] |
[4.2 -> 4.3] |
[4.3 -> 4.4] |
[4.4 -> 4.5] |
[4.5 -> 4.6] |
[4.6 -> 4.7] |
[4.8 -> 4.9] |
[FAQ Index]
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:
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.8 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 /
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.
cp /sbin/reboot /sbin/oreboot
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 xserv48.tgz tar -C / -xzphf xfont48.tgz tar -C / -xzphf xshare48.tgz tar -C / -xzphf xbase48.tgz tar -C / -xzphf game48.tgz tar -C / -xzphf misc48.tgz tar -C / -xzphf comp48.tgz tar -C / -xzphf man48.tgz tar -C / -xzphf base48.tgz # Install last! /sbin/oreboot
Again, the files in /etc are handled separately below, so etc48.tgz and xetc48.tgz are NOT unpacked here.
cd /dev ./MAKEDEV all
useradd -u 99 -g =uid -c "sndio privsep" -d /var/empty -s /sbin/nologin _sndio useradd -u 100 -g =uid -c "LDAP Daemon" -d /var/empty -s /sbin/nologin _ldapd useradd -u 101 -g =uid -c "IKEv2 Daemon" -d /var/empty -s /sbin/nologin _iked
You will want to extract the etc48.tgz files to a temporary location:
export RELEASEPATH=/usr/rel
tar -C /tmp -xzphf ${RELEASEPATH}/etc48.tgz
Note that it IS possible to locally modify these files; if this has been done, do NOT simply copy over those files, and consider using the sysmerge(8) process instead. Here are copy/paste lines for copying these files, assuming you unpacked etc48.tgz in the above recommended place:etc/daily etc/disktab etc/iked.conf etc/ksh.kshrc etc/ldapd.conf etc/netstart etc/rc etc/rc.conf etc/ldap/* etc/systrace/usr_sbin_named var/named/etc/root.hint
cd /tmp/etc mkdir -p /etc/ldap/certs cp daily disktab iked.conf ksh.kshrc ldapd.conf netstart rc rc.conf /etc cp systrace/usr_sbin_named /etc/systrace cp ldap/* /etc/ldap cp ../var/named/etc/root.hint /var/named/etc
These files likely have local changes, but should be updated for 4.8. 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. Please test this process before relying on it for a machine you can not easily get to. You can attempt to use this by executing the following as root:etc/changelist etc/ftpusers etc/mail/aliases etc/man.conf etc/newsyslog.conf etc/remote etc/services etc/ssl/x509v3.cnf etc/sysctl.conf
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 4.7, they may not accept the patch cleanly. Make sure all file changes are attempted; patch(1) may quit prematurely if it gets too confused in one file, which may happen if your machine was originally installed from a snapshot or otherwise has some interim changes. The last file to be changed here should be sysctl.conf. Deleting the file sections that fail from the patch file may permit the rest to be applied. You will need to manually apply the changes that are skipped.cd / patch -C -p0 < upgrade48.patch
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/ldpd.conf
Finally, use newaliases(8) to update the aliases database, mtree(8) create any new directories:
(note that the /etc/mtree files are now part of base48.tgz, and no longer need to be copied from etc48.tgz as they did before.)newaliases mtree -qdef /etc/mtree/4.4BSD.dist -p / -u
The 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.8-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 gives 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. You may opt to use sysmerge to make the changes, or you may wish to use the patch file first, and then follow up with a sysmerge session to clean up any loose ends.
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):
With recent improvements in sysmerge, we hope that relatively few
people have reason not to use sysmerge(8)!
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 etc48.tgz and xetc48.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:sysmerge -s $RELEASEPATH/etc48.tgz -x $RELEASEPATH/xetc48.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, chosing '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.
rm /usr/include/evdns.h rm /usr/libdata/perl5/site_perl/*-openbsd/evdns.ph rm -f /usr/bin/f77 /usr/bin/g77 /usr/include/f2c.h /usr/include/g2c.h \ /usr/lib/gcc-lib/*-unknown-openbsd*/3.3.5/f771 /usr/lib/libfrtbegin.a \ /usr/lib/libfrtbegin_p.a /usr/lib/libfrtbegin_pic.a /usr/lib/libg2c.a \ /usr/lib/libg2c_p.a /usr/lib/libg2c_pic.a /usr/share/info/g77.info \ /usr/share/man/cat1/f77.0 /usr/share/man/cat1/g77.0 cd /usr/X11R6/include/X11 rm Xaw/Print.h Xaw/PrintSP.h rm -r XprintAppUtil XprintUtil cd extensions rm Print.h Printstr.h XEVIstr.h Xagstr.h Xcupstr.h Xdbeproto.h Xevie.h \ Xeviestr.h dpmsstr.h lbxdeltastr.h lbxopts.h lbxstr.h lbxzlib.h \ mitmiscstr.h multibufst.h securstr.h shapestr.h shmstr.h syncstr.h \ xteststr.h xtrapbits.h xtrapddmi.h xtrapdi.h xtrapemacros.h \ xtraplib.h xtraplibp.h xtrapproto.h cd /usr/X11R6/lib/pkgconfig rm evieproto.pc lbxutil.pc printproto.pc trapproto.pc xaw8.pc \ xevie.pc xp.pc xprintapputil.pc xprintutil.pc xtrap.pc rm /usr/X11R6/share/aclocal/xaw.m4
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.7, it is likely you will need to modify the stock kernel of 4.8. 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.8 packages directory on your CD or nearest FTP mirror, and use something like
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.pkg_add -ui
[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.0 -> 4.1] |
[4.1 -> 4.2] |
[4.2 -> 4.3] |
[4.3 -> 4.4] |
[4.4 -> 4.5] |
[4.5 -> 4.6] |
[4.6 -> 4.7] |
[4.8 -> 4.9] |
[FAQ Index]
![[back]](../images/back.gif){kind=small}