<!doctype html>
<html lang=en id=faq>
<title>OpenBSD Upgrade Guide: 4.6 to 4.7</title>
<meta charset=utf-8>
<meta name="description" content="OpenBSD Upgrade Process for 4.6 -> 4.7">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="../openbsd.css">
<link rel="canonical" href="https://www.openbsd.org/faq/upgrade47.html">
<h2 id=OpenBSD>
<a href="../index.html">
<i>Open</i><b>BSD</b></a>
Upgrade Guide: 4.6 to 4.7
</h2>
<hr>
<p>
<a href="index.html">[FAQ Index]</a> |
<a href="upgrade46.html">[4.5 -> 4.6]</a> |
<a href="upgrade48.html">[4.7 -> 4.8]</a>
<p>
<i>Note: Upgrades are only supported from one release to the release
immediately following it.
Do not skip releases.</i>
<p><i>
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.
</i>
<p>
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.
<p>
Table of Contents:
<ul>
<li><a href="#before">Before upgrading</a>
<ul>
<li><a href="#hmac-sha2">IPsec HMAC-SHA2 incompatibility</a>
<li><a href="#newPFnat">pf(4) NAT syntax change</a>
<li><a href="#newPFrouteto">pf(4) route-to/reply-to syntax change</a>
<li><a href="#bridge">brconfig(8)/bridgename.if(5) replaced by ifconfig(8)/hostname.if(5)</a>
<li><a href="#softraid">Advance warning: Softraid metadata change (for 4.8)</a>
<li><a href="#newInstReboot">New install/reboot sequence</a>
<li><a href="#rc.conf">rc.conf</a>
<li><a href="#kern">Modified kernel</a>
</ul>
<li><a href="#upgrade">The upgrade process</a>
<li><a href="#final">Final steps</a>
<ul>
<li><a href="#UsersGroups">New and changed Users and Groups</a>
<li><a href="#etcUpgrade">Upgrading <code>/etc</code></a>
<li><a href="#patchfile">Merging locally changed files via patch file</a>
<li><a href="#sysmerge">Merging locally changed files via sysmerge(8)</a>
<li><a href="#Kernchk">Checking the kernel</a>
<li><a href="#Pkgup">Upgrading packages</a>
</ul>
</ul>
<hr>
<p>
<h2 id="before">Before upgrading: things to think about and be aware of</h2>
This is <i>not</i> a complete list of the changes that took place
between 4.6 and 4.7, 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
<a href="../plus47.html">plus47.html</a> and the CVS change logs.
<ul>
<li id="hmac-sha2">
<b>IPsec HMAC-SHA2 incompatibility:</b><br>
Two bugs in IPsec/HMAC-SHA2 were fixed, resulting in an incompatibility
with the HMAC-SHA-256/384/512 hash algorithms with previous versions of
OpenBSD and other IPsec implementations sharing the bugs.
In particular the default authentication algorithm HMAC-SHA-256 is
affected.
Upgrade both sides together, or switch to another authentication
algorithm during the transition.
<p>
<li id="newPFnat">
<b>pf(4) NAT syntax change</b><br>
As described in more detail in
<a href="https://marc.info/?l=openbsd-misc&m=125181847818600&w=2">this
mailing list post</a>, PF's separate nat/rdr/binat (translation) rules
have been replaced with actions on regular match/filter rules.
Simple rulesets may be converted like this:<p>
<pre> nat on $ext_if from 10/8 -> ($ext_if)
rdr on $ext_if to ($ext_if) -> 1.2.3.4</pre>
becomes<br>
<pre> match out on $ext_if from 10/8 nat-to ($ext_if)
match in on $ext_if to ($ext_if) rdr-to 1.2.3.4</pre><p>
and...
<pre> binat on $ext_if from $web_serv_int to any -> $web_serv_ext</pre>
becomes<br>
<pre> match on $ext_if from $web_serv_int to any binat-to $web_serv_ext</pre>
nat-anchor and/or rdr-anchor lines, e.g. for
<a href="https://man.openbsd.org/relayd">relayd(8)</a>,
<a href="https://man.openbsd.org/ftp-proxy">ftp-proxy(8)</a>
and <a href="https://man.openbsd.org/tftp-proxy">tftp-proxy(8)</a>,
are no longer used and should be removed from
<a href="https://man.openbsd.org/pf.conf">pf.conf(5)</a>,
leaving only the anchor lines. Translation rules relating to these and
<a href="https://man.openbsd.org/spamd">spamd(8)</a>
will need to be adjusted as appropriate.<p>
N.B.: Previously, translation rules had "stop at first match" behaviour,
with binat being evaluated first, followed by nat/rdr depending on direction
of the packet. Now the filter rules are subject to the usual "last match"
behaviour, so care must be taken with rule ordering when converting.
<p>
<li id="newPFrouteto">
<b>pf(4) route-to/reply-to syntax change</b>
The route-to, reply-to, dup-to and fastroute options in pf.conf
move to filteropts;
<pre>
pass in on $ext_if route-to (em1 192.168.1.1) from 10.1.1.1
pass in on $ext_if reply-to (em1 192.168.1.1) to 10.1.1.1
</pre>
becomes<br>
<pre>
pass in on $ext_if from 10.1.1.1 route-to (em1 192.168.1.1)
pass in on $ext_if to 10.1.1.1 reply-to (em1 192.168.1.1)
</pre>
<p>
<li id="bridge">
<b>brconfig(8)/bridgename.if(5) replaced by ifconfig(8)/hostname.if(5)</b><br>
The functionality of
<a href="https://man.openbsd.org/brconfig">brconfig(8)</a>
has been integrated into
<a href="https://man.openbsd.org/ifconfig">ifconfig(8)</a>.
Since the <code>priority</code> argument to set the spanning tree priority
on a bridge conflicts with the existing ifconfig(8) interface priority,
it has been renamed to <code>spanpriority</code>.
<p>
Existing /etc/bridgename.bridge* files should be replaced with
/etc/hostname.bridge* files; if you use <code>priority</code>, replace
it with <code>spanpriority</code>.
<p>
<li id="softraid">
<b>(Advance warning) Softraid metadata change:</b><br>
The metadata format used by
<a href="https://man.openbsd.org/softraid.4">softraid(4)</a>
has changed AFTER 4.7.
<del>
This WILL NOT impact your 4.6->4.7 upgrade, but will require a rebuild of
softraid(4) volumes for the 4.7 to 4.8 upgrade.
If you are doing a new softraid install, using a snapshot now is highly
recommended.
If you are upgrading an existing softraid install, start planning how
to rebuild those volumes when you later do the 4.7 to 4.8 upgrade.
</del><br>
This is no longer relevant because a transparent metadata upgrade is
performed automatically when moving to <i>-current</i>.
In the future certain softraid features might not be enabled because of
this however this will be documented.
<p>
<li id="newInstReboot">
<b>New file install/reboot sequence (non-install kernel
process)</b><br>
Previous upgrade processes used a process of install kernel,
reboot, install userland.
We now suggest a different process -- install
everything, THEN reboot.
This must be done very carefully, otherwise one could end up with a
system where the
<a href="https://man.openbsd.org/reboot.1">reboot(1)</a>
command is inoperable.
Understand and follow the directions below before doing your upgrade
remotely
<p>
<li id="rc.conf"><b>rc.conf:</b><br>
It is assumed that
<code>/etc/rc.conf</code> is not a user-altered file.
If you have made changes to your <code>/etc/rc.conf</code> file, merge those
changes into <code>/etc/rc.conf.local</code>.
If you have NO <code>/etc/rc.conf.local</code>, simply copy your existing
<code>/etc/rc.conf</code> file to <code>/etc/rc.conf.local</code> and
<i>delete the last line of the script!</i>
Otherwise, pull your existing <code>rc.conf</code> into the top of your
existing <code>rc.conf.local</code> file <i>and remove the last line</i>
before doing the rest of this process.
<p>
<li id="kern"><b>Modified kernel:</b><br>
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.7 kernel.
</ul>
<p>
<hr>
<h2 id="upgrade">The upgrade process</h2>
<h3>Upgrading by install kernel</h3>
If you have access to the system's console, the easiest and safest way
to upgrade is to boot from install media or
<a href="faq4.html#bsd.rd">bsd.rd</a> and follow the upgrade steps,
which are very similar to the <a href="faq4.html">install process</a>.
<p>
Afterwards, complete the upgrade by following the <a href="#final">final
steps</a> as detailed below.
<p>
One easy way to boot from the install kernel is to place the 4.7 version
of <i>bsd.rd</i> in the root of your boot drive, then instruct the boot loader
to boot using this new <i>bsd.rd</i> file.
On amd64 and i386, you do this by entering "<code>boot bsd.rd</code>" at the
initial <code>boot></code> prompt.
<h3>Upgrading without install kernel</h3>
<i>This is NOT the recommended process. Use the install kernel method
if at all possible!</i>
<p>
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:
<ul>
<li><b>Place install files in a "good" location</b>.
Make sure you have sufficient space!
<p>
<li><b>Stop any appropriate applications:</b>
During this process, all the userland applications will be replaced but
may not be runnable, and strange things may happen as a result.
If this is a concern to you, shut down any applications that may
be impacted.
There may be other applications which you wish to keep from running
immediately after the upgrade, stop and disable them as well.
<p>
<li><b>Check the kernel:</b>
Although <b>most people can skip this step</b>, if you had a modified kernel
in 4.6, it is likely you will need to modify the stock kernel of 4.7.
Especially when you are performing the upgrade process remotely, now is
the time to make sure the new kernel will work upon rebooting the machine.
If any changes must be made to the kernel, the safest thing to do is to
make those changes on a local 4.7 system.
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 <a href="faq5.html">FAQ 5 - Building the system from source</a>
before deciding to recompile your kernel.
<p>
<li><b>Install new kernel(s):</b>
<ul>
<li>If using a single processor kernel:
<blockquote><pre>
<b>export RELEASEPATH=</b><i>/usr/rel</i> <i># where you put the files</i>
<b>cd ${RELEASEPATH}</b>
<b>rm /obsd ; ln /bsd /obsd && cp bsd /nbsd && mv /nbsd /bsd</b>
<b>cp bsd.rd bsd.mp /</b>
</pre></blockquote>
<li>If you are using the multiprocessor kernel:
<blockquote><pre>
<b>export RELEASEPATH=</b><i>/usr/rel</i> <i># where you put the files</i>
<b>cd ${RELEASEPATH}</b>
<b>rm /obsd ; ln /bsd /obsd && cp bsd.mp /nbsd && mv /nbsd /bsd</b>
<b>cp bsd.rd /</b>
<b>cp bsd /bsd.sp</b>
</pre></blockquote>
</ul>
<p>
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.
<p>
<li><b>Save yourself a copy of the old reboot(1) command:</b>
You are still running the old kernel, it is possible the new reboot
command will not run on the old kernel.
<blockquote><pre>
<b>cp /sbin/reboot /sbin/oreboot</b>
</pre></blockquote>
<p>
<li><b>Install new userland applications.</b>
<i>Do NOT install <code>etc47.tgz</code> and <code>xetc47.tgz</code> now, because
that will overwrite your current configuration files!</i>
Note that we are installing base47.tgz LAST, because it will include a new
<a href="https://man.openbsd.org/tar.1">tar(1)</a>
utility, which may or may not run on the old kernel.
We reboot immediately, as the system is probably barely runnable now.
<blockquote><pre>
<b>tar -C / -xzphf xserv47.tgz</b>
<b>tar -C / -xzphf xfont47.tgz</b>
<b>tar -C / -xzphf xshare47.tgz</b>
<b>tar -C / -xzphf xbase47.tgz</b>
<b>tar -C / -xzphf game47.tgz</b>
<b>tar -C / -xzphf misc47.tgz</b>
<b>tar -C / -xzphf comp47.tgz</b>
<b>tar -C / -xzphf man47.tgz</b>
<b>tar -C / -xzphf base47.tgz</b> # Install last!
<b>/sbin/oreboot</b>
</pre></blockquote>
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.
<p>
Again, the files in <code>/etc</code> are handled separately below, so
<code>etc47.tgz</code> and <code>xetc47.tgz</code> are NOT unpacked here.
<p>
<li><b>After reboot completes, upgrade <code>/dev</code>.</b>
The new
<a href="https://man.openbsd.org/OpenBSD-4.7/i386/MAKEDEV">MAKEDEV</a>
file was copied to /dev by the installation of
<code>base47.tgz</code>, so you simply need to do the following:
<blockquote><pre>
<b>cd /dev</b>
<b>./MAKEDEV all</b>
</pre></blockquote>
</ul>
<hr>
<h2 id="final">Final steps</h2>
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.
<h3 id="UsersGroups">1. New Users and Groups</h3>
The following users need to be created for 4.7:
<blockquote><pre>
<b>useradd -u 97 -g =uid -c "NSD Daemon" -d /var/empty -s /sbin/nologin _nsd</b>
<b>useradd -u 98 -g =uid -c "LDP Daemon" -d /var/empty -s /sbin/nologin _ldpd</b>
</pre></blockquote>
<h3 id="etcUpgrade">2. Upgrading <code>/etc</code></h3>
<p>
You will want to extract the <code>etc47.tgz</code> files to a temporary
location:
<blockquote><pre>
<b>export RELEASEPATH=/usr/rel</b>
<b>tar -C /tmp -xzphf ${RELEASEPATH}/etc47.tgz</b>
</pre></blockquote>
Files that can probably be copied from <code>etc47.tgz</code> "as is":
<blockquote><pre>
etc/ldpd.conf
etc/moduli
etc/netstart
etc/pf.os
etc/rc
etc/rc.conf
etc/mtree/4.4BSD.dist
etc/mtree/BSD.x11.dist
etc/mtree/special
</pre></blockquote>
Note that it IS possible to locally modify these files, if this has been
done, do NOT copy over those files, and use the
<a href="#sysmerge">sysmerge(8) process</a> instead.
<!-- Pay special attention to <code>mail/*</code> if you are using something
other than the default Sendmail(8) configuration. -->
Here are copy/paste lines for copying these files, assuming you unpacked
<code>etc47.tgz</code> in the above recommended place:
<blockquote><pre>
<b>cd /tmp/etc </b>
<b>cp ldpd.conf moduli netstart pf.os rc rc.conf /etc</b>
<b>cp mtree/4.4BSD.dist mtree/BSD.x11.dist mtree/special /etc/mtree</b>
</pre></blockquote>
<p>
(YP servers only) <b>yp Makefile upgrade:</b>
Manually merge the changes of <code>/var/yp/Makefile.yp</code> (installed as
part of base47.tgz) into the Makefiles for any domains,
<code>/var/yp/*/Makefile</code>.
Practically speaking, this means copying <code>/var/yp/Makefile.yp</code> to each
domain Makefile and re-applying domain options within that file.
<h3 id="patchfile">3a. Merging locally changed files via a patch file</h3>
<p>
These files likely have local changes, but should be updated for
4.7. IF you have not altered these files, you can copy over the
new version, otherwise the changes should be merged with your files:
<blockquote><pre>
etc/changelist
etc/ftpusers
etc/ksh.kshrc
etc/mail/aliases
etc/mail/smtpd.conf
etc/newsyslog.conf
etc/protocols
etc/services
etc/sudoers
etc/sysctl.conf
var/named/etc/named-dual.conf
var/named/etc/named-simple.conf
var/named/etc/named.conf
var/named/standard/loopback6.arpa
var/www/conf/mime.types
</pre></blockquote>
The changes to these files are in <a href="upgrade47.patch">this
patch file</a>.
You can attempt to use this by executing the following as root:
<blockquote><pre>
<b>cd /</b>
<b>patch -C -p0 < upgrade47.patch</b>
</pre></blockquote>
This will test the patch to see how well it will apply to YOUR system;
to actually apply it, leave off the "<code>-C</code>" 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.6, 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.
<p>
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).
<blockquote><pre>
etc/bgpd.conf
etc/ospf6d.conf
etc/pf.conf
etc/ssh/ssh_config
etc/ssh/sshd_config
</pre></blockquote>
<p>
Finally, use
<a href="https://man.openbsd.org/newaliases.8">newaliases(8)</a>
to update the aliases database,
<a href="https://man.openbsd.org/mtree.8">mtree(8)</a>
create any new directories:
<blockquote><pre>
<b>newaliases</b>
<b>mtree -qdef /etc/mtree/4.4BSD.dist -p / -u</b>
</pre></blockquote>
<h3 id="sysmerge">3b. Merging locally changed files via sysmerge(8)</h3>
<p>
The
<a href="https://man.openbsd.org/sysmerge.8">sysmerge(8)</a>
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 <a href="faq5.html#Flavors">points in the
development process</a>, such as from an earlier <i>-current</i> to
<i>4.7-release</i> or from one <i>-current</i> 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
<a href="https://man.openbsd.org/sdiff.1">sdiff</a>.
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.
<p>
<b>Who should use sysmerge(8):</b><br>
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.
<p>
<b>Who may wish to NOT use sysmerge(8):</b><br>
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.
<p>
Please read the
<a href="https://man.openbsd.org/sysmerge.8">sysmerge(8)</a>
manual page before using it on your system.
You are also advised to read the
<a href="https://man.openbsd.org/diff.1">diff(1)</a>,
<a href="https://man.openbsd.org/sdiff.1">sdiff(1)</a>
and even review
<a href="https://man.openbsd.org/more.1">more(1)</a>
manual pages before continuing.
<p>
Assuming the <code>etc47.tgz</code> and <code>xetc47.tgz</code> files exists in
your $RELEASEPATH, run it with:
<blockquote><pre>
<b>sysmerge -s $RELEASEPATH/etc47.tgz -x $RELEASEPATH/xetc47.tgz</b>
</pre></blockquote>
Sysmerge(8) will show you a unified
<a href="https://man.openbsd.org/diff.1">diff(1)</a>,
run through your favorite $PAGER (i.e.,
<a href="https://man.openbsd.org/more.1">more(1)</a>)
and ask you, for most changed files, if you wish to:
<blockquote><pre>
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
</pre></blockquote>
<p>
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
<a href="https://man.openbsd.org/sdiff.1">sdiff(1)</a>,
where you can manually merge the file.
The default is to come back and deal with the file later, manually.
<p>
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
<a href="#UsersGroups">above</a>.
We believe it is much less error prone.
(hint: do <i>not</i> <b>i</b>nstall the temporary master.passwd file
over your existing one!).
<p>
Sysmerge(8) saves all your replaced files into a temporary directory,
similar to <code>/var/tmp/sysmerge.24959/backups</code>, so if you accidentally
clobber something that was probably not such a good idea, you have a chance
to recover it. Note that
<a href="https://man.openbsd.org/daily.8">daily(8)</a>
cleans old files from this directory.
<h3 id="Kernchk">4. Checking the kernel</h3>
Note: <b>most people can skip this step!</b>
<p>
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.6, it is likely you will need to modify the stock kernel of 4.7.
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 <a href="faq5.html">FAQ 5 - Building the system from source</a>
before considering to recompile your kernel.
<h3 id="Pkgup">5. Upgrading packages</h3>
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.
<p>
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.
<ul>
<li><b>postgresql:</b> You must dump your databases before upgrading and
reload them after.
<li><b>kqemu:</b> Must be kept in sync with the kernel. pkg_delete prior
to the upgrade, then pkg_add the new package once the upgrade has been
completed.
<li><b>bacula:</b> has a new catalog format which requires a database
schema change on the director.
The
<a href="https://cvsweb.openbsd.org/ports/sysutils/bacula/Makefile#rev1.16">commit
log entry</a> and
release notes have more details.
<li><b>asterisk:</b> You may need to make some configuration changes;
please see /usr/local/share/doc/asterisk/UPGRADE-16.txt.
The old app_conference plugin is incompatible with the new version, you
must use appkonference instead.
</ul>
<p>
The package tools support in-place updating using <code>pkg_add -u</code>.
For instance, to update all your packages, make sure <code>PKG_PATH</code> is
pointing to the 4.7 packages directory on your CD or nearest FTP mirror,
and use something like
<blockquote><pre>
<b>pkg_add -ui -D update -D updatedepends</b>
</pre></blockquote>
where the <code>-u</code> indicates update mode, and <code>-i</code> specifies
interactive mode, so pkg_add will prompt you for input when it encounters
some ambiguity. Read the
<a href="https://man.openbsd.org/OpenBSD-4.7/pkg_add">pkg_add(1)</a>
manual page and the <a href="faq15.html">package management</a>
chapter of the FAQ for more information.
<p>
Two packages now come with perl 5.10.1 in base.
If you have installed these packages, delete them now:
<blockquote><pre>
<b>pkg_delete p5-parent p5-Parse-CPAN-Meta</b>
</pre></blockquote>
<p>
<a href="index.html">[FAQ Index]</a> |
<a href="upgrade46.html">[4.5 -> 4.6]</a> |
<a href="upgrade48.html">[4.7 -> 4.8]</a>
<hr>
<small>$OpenBSD: upgrade47.html,v 1.31 2021/03/15 10:18:43 jsg Exp $</small>
![[BACK]](/icons/back.gif){kind=icon}
Return to upgrade47.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www / faq