File: [local] / www / faq / upgrade73.html (download) (as text)
Revision 1.4, Thu May 2 19:32:53 2024 UTC (5 weeks ago) by sthen
Branch: MAIN
CVS Tags: HEAD
Changes since 1.3: +2 -2 lines
fix section number for fw_update manual, it moved from 1 to 8 in 7.1
|
<!doctype html>
<html lang=en id=faq>
<title>OpenBSD Upgrade Guide: 7.2 to 7.3</title>
<meta charset=utf-8>
<meta name="description" content="OpenBSD Upgrade Process for 7.2 -> 7.3">
<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/upgrade73.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: 7.2 to 7.3
</h2>
<hr>
<p>
<a href="index.html">[FAQ Index]</a> |
<a href="upgrade72.html">[7.1 -> 7.2]</a>
<a href="upgrade74.html">[7.3 -> 7.4]</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.3/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="upgrade73.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.3/alpha/bsd.rd">alpha</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/amd64/bsd.rd">amd64</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/arm64/bsd.rd">arm64</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/armv7/bsd.rd">armv7</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/hppa/bsd.rd">hppa</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/i386/bsd.rd">i386</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/landisk/bsd.rd">landisk</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/luna88k/bsd.rd">luna88k</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/macppc/bsd.rd">macppc</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/octeon/bsd.rd">octeon</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/powerpc64/bsd.rd">powerpc64</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/riscv64/bsd.rd">riscv64</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/sparc64/bsd.rd">sparc64</a>]
</dd>
<dt><code>SHA256.sig</code></dt>
<dd>
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/alpha/SHA256.sig">alpha</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/amd64/SHA256.sig">amd64</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/arm64/SHA256.sig">arm64</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/armv7/SHA256.sig">armv7</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/hppa/SHA256.sig">hppa</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/i386/SHA256.sig">i386</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/landisk/SHA256.sig">landisk</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/luna88k/SHA256.sig">luna88k</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/macppc/SHA256.sig">macppc</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/octeon/SHA256.sig">octeon</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/powerpc64/SHA256.sig">powerpc64</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/riscv64/SHA256.sig">riscv64</a>]
[<a href="https://cdn.openbsd.org/pub/OpenBSD/7.3/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.3/signify">signify(1)</a>:
<pre class="cmdbox">
$ <b>signify -C -p /etc/signify/openbsd-73-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="upgrade73.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.3/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="../errata73.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.3/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.3/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.3/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>base73.tgz</code> last, because the new base system,
in particular <a href="https://man.openbsd.org/OpenBSD-7.3/tar">tar(1)</a>,
<a href="https://man.openbsd.org/OpenBSD-7.3/gzip">gzip(1)</a> and
<a href="https://man.openbsd.org/OpenBSD-7.3/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 xshare73.tgz</b>
# <b>tar -C / -xzphf xserv73.tgz</b>
# <b>tar -C / -xzphf xfont73.tgz</b>
# <b>tar -C / -xzphf xbase73.tgz</b>
# <b>tar -C / -xzphf man73.tgz</b>
# <b>tar -C / -xzphf game73.tgz</b>
# <b>tar -C / -xzphf comp73.tgz</b>
# <b>tar -C / -xzphf base73.tgz</b> # Install last!
# <b>/sbin/oreboot</b><!--
--></pre>
or, if you use
<a href="https://man.openbsd.org/OpenBSD-7.3/ksh">ksh(1)</a>, you can do:
<pre class="cmdbox">
# <b>cp /sbin/reboot /sbin/oreboot</b>
# <b>for _f in [!b]*73.tgz base73.tgz; do tar -C / -xzphf "$_f" || break; done</b>
# <b>/sbin/oreboot</b><!--
--></pre>
Note that <a href="https://man.openbsd.org/OpenBSD-7.3/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.3/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.3/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.3/fw_update">fw_update(8)</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>TCP timer sysctls <code>net.inet.tcp.keepidle</code> and
<code>net.inet.tcp.keepintvl</code></b>
<code>net.inet.tcp.keepidle</code> and <code>net.inet.tcp.keepintvl</code>
are now specified in seconds.<p>
<p>
They were previously specified in units of a clock ticking
<code>net.inet.tcp.slowhz</code> times per second (typically, half-seconds).
<p>
If you have changed them, you may need to adapt them.
<p>
<li><b>tftpd(8).</b> <a href="https://man.openbsd.org/tftpd.8">tftpd(8)</a>
now serves files in read-only mode.
<p>
Use the new <code>-w</code> option to enable write access (old default).
</ul>
<h3 id="RmFiles">Files to remove</h3>
<ul>
<li>Nothing to remove this release
</ul>
<h3 id="SpecialPackages">Special packages</h3>
<ul>
<li><b>gitea.</b>
The gitea static files location was changed from
<code>/usr/local/share/gitea/public/</code> to
<code>/var/www/gitea/public/</code> and
<code>/usr/local/share/gitea/public</code> is now a symlink to
<code>/var/www/gitea/public/</code>. This allows serving static files
by local http server for better performance.
<p>
Due to <code>/usr/local/share/gitea/public</code> changing from
a directory to a symlink, upgrading the gitea package using
<code>pkg_add -u</code> will fail.
<p>
To upgrade, delete gitea package, then add the updated version:
<pre class="cmdbox">
# pkg_delete gitea && pkg_add gitea<!--
--></pre>
<p>
<li><b>gotweb.</b>
The gotweb package has been removed since it is no longer maintained
upstream. The successor to gotweb is gotwebd, which serves FastCGI
directly rather than relying on
<a href="https://man.openbsd.org/slowcgi.8">slowcgi(8)</a> and www/kcgi
as gotweb did. gotwebd provides improved performance and caching.
<p>
Users should install the gotwebd package:
<pre class="cmdbox">
# pkg_add gotwebd<!--
--></pre>
<p>
Setting up gotwebd is similar to setting up gotweb.
Instructions are provided in manual pages installed by the
gotwebd package:
<ul>
<li><a href="https://gameoftrees.org/gotwebd.8.html">gotwebd(8)</a>
<li><a href="https://gameoftrees.org/gotwebd.conf.5.html">gotwebd.conf(5)</a>
</ul>
<p>
Before removing the gotweb package, gotwebd can be configured in
<a href="https://man.openbsd.org/httpd.conf.5">httpd.conf(5)</a>
to serve the same set of Git repositories under a different URL location,
for testing purposes.
<p>
Once gotwebd works as expected,
<a href="https://man.openbsd.org/httpd.8">httpd(8)</a> can be reconfigured
to expose the former gotweb URL location using gotwebd, and the gotweb package
can be removed:
<pre class="cmdbox">
# pkg_delete gotweb<!--
--></pre>
<p>
<li><b>postgresql.</b>
There was a major update to PostgreSQL 15.1. Use <code>pg_upgrade</code>
as described in the postgresql-server pkg-readme or do a dump/restore.
<p>
<li><b>puppet / puppetdb.</b>
Puppet and Puppetdb 5, and with that, the ability to run Puppet in master
mode were removed. As their successors, Puppet, Puppetdb and Puppetserver
7 were added.
<p>
Users who intend to run a Puppet server should install the puppetserver
package:
<pre class="cmdbox">
# pkg_add puppetserver<!--
--></pre>
<p>
The new Puppetserver requires some initial bootstrapping, which is described
in <code>/usr/local/share/doc/pkg-readmes/puppetserver</code>.
<p>
<li><b>python.</b>
Python 3.10 is now the default. Python 3.9 is scheduled to be removed
before the OpenBSD 7.4 release.
</ul>
<a href="index.html">[FAQ Index]</a> |
<a href="upgrade72.html">[7.1 -> 7.2]</a>
<a href="upgrade74.html">[7.3 -> 7.4]</a>
<hr>
<small>$OpenBSD: upgrade73.html,v 1.4 2024/05/02 19:32:53 sthen Exp $</small>
![[BACK]](/icons/back.gif){kind=icon}
Return to upgrade73.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www / faq