File: [local] / www / faq / upgrade70.html (download) (as text)
Revision 1.4, Wed Apr 20 15:55:48 2022 UTC (2 years, 1 month ago) by kmos
Branch: MAIN
CVS Tags: HEAD
Changes since 1.3: +1 -5 lines
Uncomment links to upgrade71.html
|
<!doctype html>
<html lang=en id=faq>
<title>OpenBSD Upgrade Guide: 6.9 to 7.0</title>
<meta charset=utf-8>
<meta name="description" content="OpenBSD Upgrade Process for 6.9 -> 7.0">
<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/upgrade70.html">
<style>
dt { margin-left: 20px; float: left; }
dd { margin: 0 0 0 8em; }
</style>
<h2 id=OpenBSD>
<a href="../index.html">
<i>Open</i><b>BSD</b></a>
Upgrade Guide: 6.9 to 7.0
</h2>
<hr>
<p>
<a href="index.html">[FAQ Index]</a> |
<a href="upgrade69.html">[6.8 -> 6.9]</a>
<a href="upgrade71.html">[7.0 -> 7.1]</a>
<p>
<blockquote>
<p><i>
Upgrades are only supported from one release to the release immediately
following.</i>
<p>
<strong><i>Read through and understand this process before attempting it.
For critical or physically remote machines, test it on an identical,
local system first.
</i></strong></blockquote>
<h3 id="BeforeUpdate">Before using any upgrade method</h3>
<ul>
<li><b>Check available disk space in /usr.</b>
Verify that the <code>/usr</code> partition has a size of at least 1.1G.
With less space the upgrade may fail and you should consider reinstalling
the system instead.
<p>
<li><b>Read configuration and syntax changes and the
package upgrade instructions.</b>
There were several <a href="#ConfigChanges">configuration changes</a>
and <a href="#SpecialPackages">changes in packages</a> that may
require planning before starting the upgrade.
</ul>
<h3 id="UpgradeMethods">Upgrade Methods</h3>
<ul>
<li><b>Unattended Upgrade:</b>
The easiest method is an unattended upgrade using
<a href="https://man.openbsd.org/OpenBSD-7.0/sysupgrade.8">sysupgrade(8)</a>.
The program will download all the install sets, verify their signatures, and
reboot to perform the upgrade automatically. Once the unattended upgrade has
completed, continue <a href="upgrade70.html#AfterSets">below</a>.
<p>
<li><b>Interactive Upgrade:</b>
If you insist on leaving out some of the install sets, you will want to
perform an <a href="#InteractiveUpgrade">interactive upgrade</a>. (sysupgrade
upgrades with all install sets.)
<p>
<li><b>Manual Upgrade:</b>
The final option is using the <a href="#NoInstKern">manual upgrade process</a>.
(This is not recommended as it is the most error-prone method.)
</ul>
<hr>
<h3 id="InteractiveUpgrade">Interactive Upgrade</h3>
<ul>
<li><b>Get and verify <code>bsd.rd</code>.</b>
Download the ramdisk kernel and the cryptographically-signed checksum file
for your architecture.
<p>
<dl>
<dt><code>bsd.rd</code></dt>
<dd>
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/alpha/bsd.rd">alpha</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/amd64/bsd.rd">amd64</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/arm64/bsd.rd">arm64</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/armv7/bsd.rd">armv7</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/hppa/bsd.rd">hppa</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/i386/bsd.rd">i386</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/landisk/bsd.rd">landisk</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/loongson/bsd.rd">loongson</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/luna88k/bsd.rd">luna88k</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/macppc/bsd.rd">macppc</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/octeon/bsd.rd">octeon</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/powerpc64/bsd.rd">powerpc64</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/sparc64/bsd.rd">sparc64</a>]
</dd>
<dt><code>SHA256.sig</code></dt>
<dd>
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/alpha/SHA256.sig">alpha</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/amd64/SHA256.sig">amd64</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/arm64/SHA256.sig">arm64</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/armv7/SHA256.sig">armv7</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/hppa/SHA256.sig">hppa</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/i386/SHA256.sig">i386</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/landisk/SHA256.sig">landisk</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/loongson/SHA256.sig">loongson</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/luna88k/SHA256.sig">luna88k</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/macppc/SHA256.sig">macppc</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/octeon/SHA256.sig">octeon</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/powerpc64/SHA256.sig">powerpc64</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.0/sparc64/SHA256.sig">sparc64</a>]
</dd>
</dl>
<p>
Verify <code>bsd.rd</code> and <code>SHA256.sig</code> using
<a href="https://man.openbsd.org/OpenBSD-7.0/signify">signify(1)</a>:
<pre class="cmdbox">
$ <b>signify -C -p /etc/signify/openbsd-70-base.pub -x SHA256.sig bsd.rd</b>
Signature Verified
bsd.rd: OK<!--
--></pre>
<p>
<li> Next, boot from the install kernel, <code>bsd.rd</code>, retrieved
in the previous step. Place it in the root of your filesystem and
instruct the boot loader to boot this kernel. Once this kernel is
booted, choose the <code>(U)pgrade</code> option and follow the prompts.
<p>
<li>After the filesets have been installed, the system will reboot with
the upgraded kernel. Now continue <a
href="upgrade70.html#AfterSets">with the next step</a>:
</ul>
<hr>
<h3 id="AfterSets">After the Upgrade</h3>
<p>
After upgrading the sets, the system will reboot with the upgraded
kernel and run <a
href="https://man.openbsd.org/OpenBSD-7.0/sysmerge">sysmerge(8)</a>
during boot. In some cases, configuration files cannot be modified
automatically. Run
<pre class="cmdbox"> # <b>sysmerge</b><!-- --></pre>
to check and perform these <a href="#ConfigChanges">configuration
changes</a>.
<p>Next <a href="#RmFiles">remove the old files</a>.
Finish up by upgrading the packages using <code><b>pkg_add -u</b></code>.
<p>
You may wish to check the <a href="../errata70.html">errata page</a> for
any post-release fixes.
<p>
<hr>
<h2 id="NoInstKern">Manual Upgrade (without the install kernel)</h2>
<b style="color:#e00000">This is NOT the recommended process.
Use the unattended or interactive upgrade methods if at all possible!</b>
<p>
Sometimes, you need to perform an upgrade of a machine for which the normal
unattended or interactive upgrade process is not possible.
<h3>Preparation</h3>
<ul>
<li><b>Place install files in a good location.</b>
Make sure you have sufficient space!
Running out of space on a remote upgrade could be...unfortunate.
Note that using softdeps can exacerbate the situation as deleted and
overwritten files do not release their space immediately.
Consider disabling the <code>softdep</code> mount option in
<code>/etc/fstab</code> and rebooting before undertaking a manual upgrade.
Having at least 500MB free on <code>/usr</code> would be recommended.
<p>
<li><b>Become root.</b>
While using
<a href="https://man.openbsd.org/OpenBSD-7.0/doas">doas(1)</a>
before each command is generally a good practice, the command will likely
be broken by the last steps, so you should become root before starting
this process.
It might be good to verify your access to root using a method other than
doas at this point, i.e., direct login or using
<a href="https://man.openbsd.org/OpenBSD-7.0/su">su(1)</a>.
<p>
<li><b>Stop and/or disable 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.
You may also have issues with DNS resolution during the first reboot, so
PF rules and NFS mounts dependent upon DNS may cause boot-up problems.
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>Install new boot blocks.</b>
This should actually be done at the end of any upgrade.
If this has been neglected, then failure to do this now may break serial
console or other things, depending on your platform.
Use <a href="https://man.openbsd.org/OpenBSD-7.0/amd64/installboot">
installboot(8)</a>, assuming <code>sd0</code> is your boot disk:
<pre class="cmdbox">
# <b>installboot sd0</b><!--
--></pre>
</ul>
<h3>Upgrading manually</h3>
<ul>
<li><b>Install new kernels.</b>
The extra steps for copying over the primary kernel are done
to ensure that there is always a valid kernel on the disk.
<p>
If using the multiprocessor kernel:
<pre class="cmdbox">
# <b>cd /usr/rel</b> # where you put the release files
# <b>ln -f /bsd /obsd && cp bsd.mp /nbsd && mv /nbsd /bsd</b>
# <b>cp bsd.rd /</b>
# <b>cp bsd /bsd.sp</b><!--
--></pre>
If using the single processor kernel:
<pre class="cmdbox">
# <b>cd /usr/rel</b> # where you put the release files
# <b>ln -f /bsd /obsd && cp bsd /nbsd && mv /nbsd /bsd</b>
# <b>cp bsd.rd bsd.mp /</b> # may give a harmless warning<!--
--></pre>
<p>
<li><b>Enable KARL.</b>
Store the kernel's checksum:
<pre class="cmdbox">
# <b>sha256 -h /var/db/kernel.SHA256 /bsd</b> <!--
--></pre>
<p>
<li><b>Install new userland.</b>
Save a copy of reboot(8), extract and install the release tarballs, reboot.
Install <code>base70.tgz</code> last, because the new base system,
in particular <a href="https://man.openbsd.org/OpenBSD-7.0/tar">tar(1)</a>,
<a href="https://man.openbsd.org/OpenBSD-7.0/gzip">gzip(1)</a> and
<a href="https://man.openbsd.org/OpenBSD-7.0/reboot">reboot(8)</a>,
will not work with the old kernel.
Either untar the needed filesets manually:
<pre class="cmdbox">
# <b>cp /sbin/reboot /sbin/oreboot</b>
# <b>tar -C / -xzphf xshare70.tgz</b>
# <b>tar -C / -xzphf xserv70.tgz</b>
# <b>tar -C / -xzphf xfont70.tgz</b>
# <b>tar -C / -xzphf xbase70.tgz</b>
# <b>tar -C / -xzphf man70.tgz</b>
# <b>tar -C / -xzphf game70.tgz</b>
# <b>tar -C / -xzphf comp70.tgz</b>
# <b>tar -C / -xzphf base70.tgz</b> # Install last!
# <b>/sbin/oreboot</b><!--
--></pre>
or, if you use
<a href="https://man.openbsd.org/OpenBSD-7.0/ksh">ksh(1)</a>, you can do:
<pre class="cmdbox">
# <b>cp /sbin/reboot /sbin/oreboot</b>
# <b>for _f in [!b]*70.tgz base70.tgz; do tar -C / -xzphf "$_f" || break; done</b>
# <b>/sbin/oreboot</b><!--
--></pre>
Note that <a href="https://man.openbsd.org/OpenBSD-7.0/tar">tar(1)</a>
can expand only one archive per invocation, so a simple glob won't work.
<p>
<li><b>After reboot, update <code>/dev</code>.</b>
Run
<a href="https://man.openbsd.org/OpenBSD-7.0/amd64/MAKEDEV">MAKEDEV(8)</a>:
<pre class="cmdbox">
# <b>cd /dev</b>
# <b>./MAKEDEV all</b><!--
--></pre>
<p>
<li><b>Update the boot loader.</b>
Still assuming <code>sd0</code> is your boot disk:
<pre class="cmdbox">
# <b>installboot sd0</b><!--
--></pre>
<p>
<li><b>Update system configuration files.</b>
Run <a href="https://man.openbsd.org/OpenBSD-7.0/sysmerge">sysmerge(8)</a>:
<pre class="cmdbox">
# <b>sysmerge</b><!--
--></pre>
<p>
<li><b>Update firmware.</b>
There may be new firmware for your system.
Update it with
<a href="https://man.openbsd.org/OpenBSD-7.0/fw_update">fw_update(1)</a>:
<pre class="cmdbox">
# <b>fw_update</b><!--
--></pre>
<p>
<li><b>Finish up.</b>
Review the console output from boot (using <code><b>dmesg -s</b></code>)
and correct any failures as necessary.
All the steps following <a href="#ConfigChanges">configuration changes</a>
below also apply to manual upgrades.
Finally, remove <code><b>/sbin/oreboot</b></code> and update packages:
<code><b>pkg_add -u</b></code>.
Reboot once more to make sure you use the newest firmware files
and run on your own kernel generated by KARL.
</ul>
<p>
<hr>
<h3 id="ConfigChanges">Configuration and syntax changes</h3>
<ul>
<li><b>snmpd(8).</b>
Default security settings have been tightened.
<ul>
<li>The default protocol has changed to SNMPv3.
<li>The default communities <code>public</code> and <code>private</code>
have been removed. Communities must now be set explicitly.
<li><code>seclevel</code> default changed from <code>none</code>
to <code>enc</code>.
<li>The default SNMPv3 encryption has changed to AES.
<li>The protocol version for <code>trap receiver</code> (for sending traps
to another host) no longer defaults to SNMPv2.
</ul>
<p>To configure SNMPv3, you will need to add one or more users to
the configuration, e.g.:
<pre class="cmdbox">
user "manager" authkey "XblueQ300ZyAbUIbndmWjfl" auth hmac-sha1 enc aes enckey "tVadj9jxq8rdJ"<!--
--></pre>
<p>If you need to reinstate SNMPv1/v2c, you can add something like the
following to <code>snmpd.conf(5)</code>
<pre class="cmdbox">
listen on any snmpv1 snmpv2c read
read-only community U9PeBY1694bcxMnm
seclevel none<!--
--></pre>
<p>The community name should not be common or easily brute-forced,
especially if exposed to the internet.
<li><b>snmp(1).</b>
<ul>
<li>The default protocol version has changed from v2c to v3.
<li>The default encryption has changed to AES.
<li>The default authentication has changed to SHA1.
<li>
The default community <code>public</code> has been removed.
</ul>
</ul>
<h3 id="RmFiles">Files to remove</h3>
<ul>
<li>
The dmx library was removed.
<pre class="cmdbox">
# rm -f /usr/X11R6/lib/libdmx.* \
/usr/X11R6/include/X11/extensions/dmxext.h \
/usr/X11R6/lib/pkgconfig/dmx.pc \
/usr/X11R6/man/man3/DMX*.3<!--
--></pre>
<p>
<li>A more detailed cleanup can be done with the aid of the sysclean package.
</ul>
<h3 id="SpecialPackages">Special packages</h3>
<ul>
<li><b>net/freeradius.</b>
FreeRADIUS removed LEAP in 3.0.22. This was previously in the default
configuration, so if you have enabled EAP you are likely to need
to update /etc/raddb/mods-available/eap and remove the
<code>leap { ... }</code> lines.
</ul>
<p>
<a href="index.html">[FAQ Index]</a> |
<a href="upgrade69.html">[6.8 -> 6.9]</a>
<a href="upgrade71.html">[7.0 -> 7.1]</a>
<hr>
<small>$OpenBSD: upgrade70.html,v 1.4 2022/04/20 15:55:48 kmos Exp $</small>
![[BACK]](/icons/back.gif){kind=icon}
Return to upgrade70.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www / faq