File: [local] / www / faq / upgrade52.html (download) (as text)
Revision 1.32, Sun Apr 9 07:14:45 2023 UTC (13 months, 2 weeks ago) by jsg
Branch: MAIN
CVS Tags: HEAD
Changes since 1.31: +2 -2 lines
fix double words
|
<!doctype html>
<html lang=en id=faq>
<title>OpenBSD Upgrade Guide: 5.1 to 5.2</title>
<meta charset=utf-8>
<meta name="description" content="OpenBSD Upgrade Process for 5.1 -> 5.2">
<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/upgrade52.html">
<h2 id=OpenBSD>
<a href="../index.html">
<i>Open</i><b>BSD</b></a>
Upgrade Guide: 5.1 to 5.2
</h2>
<hr>
<p>
<a href="index.html">[FAQ Index]</a> |
<a href="upgrade51.html">[5.0 -> 5.1]</a> |
<a href="upgrade53.html">[5.2 -> 5.3]</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="#raidframe">raid(4) and RAIDframe are no more</a>
<li><a href="#radeon">Radeon X driver changes</a>
<li><a href="#OpenSMTPd">OpenSMTPd changes</a>
<li><a href="#pf">Packet Filter changes</a>
<li><a href="#tftpd">tftpd starts from rc.d now</a>
<li><a href="#nginx">Introducing nginx</a>
</ul>
<li><a href="#upgrade">The upgrade process</a>
<li><a href="#final">Final steps</a>
<ul>
<li><a href="#sysmerge">Merging locally changed files via sysmerge(8)</a>
<li><a href="#patchfile">Merging locally changed files via patch file</a>
<li><a href="#RmFiles">Files to delete</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 5.1 and 5.2, 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="../plus51.html">plus51.html</a> and the CVS change logs.
<ul>
<li id="raidframe"><b>raid(4) and RAIDframe are no more:</b>
If you are using RAIDframe for a system currently, you will need to make
plans to rebuild it using
<a href="https://man.openbsd.org/softraid.4">softraid(4)</a>
before you can upgrade it past 5.1.
<p>
<li id="radeon"><b>Radeon X driver changes:</b>
The
<a href="https://man.openbsd.org/radeon">radeon(4)</a>
driver has been updated to version 6.14.3, but it's not selected by
auto-configuration code.
The
<a href="https://man.openbsd.org/radeonold">radeonold(4)</a>
driver is providing a frozen version of the last working driver, as
there were some issues with the new driver.
Users with cards needing the new driver should create an
<a href="https://man.openbsd.org/xorg.conf">xorg.conf(5)</a>
file containing just
<pre>
Section "Device"
Identifier "RadeonCard"
Driver "radeon"
EndSection
</pre>
Or merge this section in their existing <code>/etc/X11/xorg.conf</code> file.
<p>
The <b>radeonhd</b> driver is now deprecated.
Users of this driver should update their <code>/etc/X11/xorg.conf</code> file
by replacing
<pre>
Driver "radeonhd"
</pre>
with
<pre>
Driver "radeon"
</pre>
<p>
<li id="OpenSMTPd"><b>OpenSMTPd changes:</b>
<ul>
<li><b>smtpd.conf syntax changes:</b>
<ul>
<li><code>relay via</code> rules should now be expressed with a relay URL:
<pre> accept [...] relay via "mx1.example.org" smtps port 465</pre>
becomes
<pre> accept [...] relay via "smtps://mx1.example.org"</pre>
<li>makemap(8) virtual domains configuration:
<pre> accept for virtual vmap [...]</pre>
becomes
<pre> accept for virtual map vmap [...]</pre>
</ul>
The new syntax is documented in
<a href="https://man.openbsd.org/smtpd.conf.5">smtpd.conf(5)</a>
<p>
<li><b>smtpd queue layout changed:</b>
A change to the queue layout was introduced, you will want to empty your
queue before updating.
</ul>
<p>
<li id="pf"><b>pf.conf syntax changes:</b>
<ul>
<li><code>prio</code> to assign queueing priorities has changed to <code>set prio</code>.
<li><code>set-tos</code> to enforce a TOS has changed to <code>set tos</code>
</ul>
The new syntax is documented in
<a href="https://man.openbsd.org/pf.conf.5">pf.conf(5)</a>
<p>
<li id="tftpd"><b>tftpd starts from rc.d now:</b>
keeping with newer practices,
<a href="https://man.openbsd.org/tftpd.8">tftpd(8)</a>
is no longer run from
<a href="https://man.openbsd.org/inetd.8">inetd(8)</a>
but is now started using an rc.d script.
You will want to remove the tftpd lines from <code>/etc/inetd</code> and
replace them with a <code>tftpd_flags="<i>[chroot directory]</i>"</code>
line in <code>/etc/rc.conf.local</code>.
<p>
<li id="nginx"><b>Introducing nginx(8):</b>
<a href="https://nginx.org">nginx</a> (see also
<a href="https://man.openbsd.org/nginx.8">nginx(8)</a>)
has been added to OpenBSD, ultimately to replace the Apache 1.3 derived
<a href="https://man.openbsd.org/httpd.8">httpd(8)</a>.
For new installations, you are encouraged to utilize nginx rather than
httpd, existing installations are encouraged to start planning replacing
the stock httpd with nginx.
</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 the install kernel by boot 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 5.2 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>Become root with ksh(1):</b>
While using
<a href="https://man.openbsd.org/sudo.8">sudo(8)</a>
before each command is generally a good practice, the sudo(8) command
will be broken by the last steps, so you should be root before starting
this process.
Also, the use of the OpenBSD
<a href="https://man.openbsd.org/ksh.1">ksh(1)</a>
shell is assumed.
<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>Disable package daemons and local shutdown commands:</b>
The last steps in the upgrade process may result in various commands,
especially those which are dynamically linked, being broken.
In particular, this may prevent a normal shutdown of daemons listed
in pkg_scripts, or additional commands in /etc/rc.shutdown, which may
cause the machine to hang at shutdown.
Before you proceed with the upgrade, edit /etc/rc.conf.local and
comment-out any pkg_scripts lines.
Also inspect /etc/rc.shutdown and comment-out any local shutdown commands.
These can be reinstated post upgrade.
<p>
<li><b>Check the kernel:</b>
Although <b>most people can skip this step</b>, if you had a modified kernel
in 5.1, it is likely you will need to modify the stock kernel of 5.2.
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 5.2 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>
(note: you will get a harmless error message if your platform doesn't
have a bsd.mp):
<p>
<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 a copy of reboot(8), install new userland applications.</b>
You are still running the old kernel, it is possible the new reboot
command will not run on the old kernel, so we will start by saving a
copy of the old reboot command.
<i>Do NOT install <code>etc52.tgz</code> and <code>xetc52.tgz</code> now, because
that will overwrite your current configuration files!</i>
Note that we are installing base52.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 after
the unpacking of all the new files.
<blockquote><pre>
<b>cp /sbin/reboot /sbin/oreboot</b>
<b>tar -C / -xzphf xserv52.tgz</b>
<b>tar -C / -xzphf xfont52.tgz</b>
<b>tar -C / -xzphf xshare52.tgz</b>
<b>tar -C / -xzphf xbase52.tgz</b>
<b>tar -C / -xzphf game52.tgz</b>
<b>tar -C / -xzphf comp52.tgz</b>
<b>tar -C / -xzphf man52.tgz</b>
<b>tar -C / -xzphf base52.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>etc52.tgz</code> and <code>xetc52.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-5.2/i386/MAKEDEV">MAKEDEV</a>
file was copied to /dev by the installation of
<code>base52.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, you need to update
the system configuration files which are included in the <code>etc52.tgz</code>
which have not been dealt with so far.
There are two processes we provide for you -- manually copying over some
files and patching others, or using the
<a href="https://man.openbsd.org/sysmerge.8">sysmerge(8)</a>
process.
<p>
<h3 id="sysmerge">1a. Merging locally changed files via sysmerge(8)</h3>
<blockquote>
<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 part way 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>
With recent improvements in sysmerge, we hope that relatively few
people have reason not to use sysmerge(8)!
However, people with a large quantity of similar machines to upgrade
may find the "patch file" process faster, and perhaps the basis of
a customized upgrade script.
<p>
<b>Using sysmerge(8) for the first time:</b><br>
If you have a system that's been upgraded in the past via the patch file
process you will probably find the FIRST time you upgrade by sysmerge,
you have a LOT of manual file changes to make.
This is because the patch file process only attempted to achieve
functional compatibility on the upgraded system, and did not respect
the version control information sysmerge(8) uses to identify "unchanged"
files.
Rest assured, later runs of sysmerge will be far less painful, and often
completely effortless.
<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 in 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>5.1-current</i> to
<i>5.2-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 what would have
been there from the last run of sysmerge.
Usually, it can figure out what to do to update your files, but if it
has difficulty, it will give 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>.
<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>etc52.tgz</code> and <code>xetc52.tgz</code> files exists in
your ${RELEASEPATH}, run it with:
<blockquote><pre>
<b>sysmerge -s ${RELEASEPATH}/etc52.tgz -x ${RELEASEPATH}/xetc52.tgz</b>
</pre></blockquote>
For the files sysmerge(8) can't resolve on its own, it 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 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>
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, but it will survive a reboot.
<!-- p>
<b>Sysmerge notes for 5.1 -> 5.2:</b><br>
<ul>
<li><b><code>/etc/sysctl.conf</code>:</b>
The changes to <code>sysctl.conf</code> are all commented out items, so not
installing the changed file will not directly change your system's
behaviour.
Blindly installing the new default over your old, customized file
will often cause significant annoyance.
However, the new file shows the defaults and common options that are
available, so you may wish to manually merge the changes into your file,
or install the new file and put your changes back into the new file.
</ul -->
</blockquote>
<p>
<h3 id="patchfile">1b. Merging locally changed files via a patch file</h3>
<blockquote>
This process makes a lot of assumptions about what files you have and
have not modified, and that you are upgrading from <i>5.1-release</i> to
<i>5.2-release</i>.
Before following this, make sure your system matches the assumptions,
and alter the process accordingly if needed -- or just use the above
<a href="#sysmerge">sysmerge process</a>.
<p id="UsersGroups">
No new users and groups need to be created for 5.2.
<!--
The following users need to be created for 4.8:
<blockquote><pre>
<b>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</b>
</pre></blockquote>
-->
<p>
You will want to extract the <code>etc52.tgz</code> files to a temporary
location:
<blockquote><pre>
<b>export RELEASEPATH=/usr/rel</b>
<b>tar -C /tmp -xzphf ${RELEASEPATH}/etc52.tgz</b>
</pre></blockquote>
Files that can probably be copied from <code>etc52.tgz</code> "as is":
<blockquote><pre>
etc/daily
etc/moduli
etc/rc
etc/rc.conf
etc/mail/localhost.cf
etc/mail/sendmail.cf
etc/mail/submit.cf
etc/rc.d/nfsd
etc/rc.d/nginx
etc/rc.d/sendmail
etc/rc.d/tftpd
etc/rc.d/rc.subr
var/www/conf/bgplg.head
</pre></blockquote>
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
<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.
<p>
Here are copy/paste lines for copying these files, assuming you unpacked
<code>etc52.tgz</code> in the above recommended place:
<blockquote><pre>
<b>cd /tmp/etc</b>
<b>cp daily moduli rc rc.conf /etc</b>
<b>mkdir /etc/nginx</b>
<b>cp nginx/* /etc/nginx/</b>
<b>cd /tmp/etc/rc.d</b>
<b>cp nfsd nginx sendmail tftpd rc.subr /etc/rc.d</b>
<b>cp /tmp/var/www/conf/bgplg.head /var/www/conf/</b>
<b>cp /tmp/etc/mail/*.cf /etc/mail</b> # <i>Use with care!</i>
</pre></blockquote>
<p>
<p>
These files likely have local changes, but should be updated for
5.2. 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/inetd.conf
etc/login.conf
etc/services
etc/sysctl.conf
etc/mail/smtpd.conf
etc/mail/spamd.conf
etc/ssh/sshd_config
</pre></blockquote>
The changes to these files are in <a href="upgrade52.patch">this
patch file</a>.
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:
<blockquote><pre>
<b>cd /</b>
<b>ftp http://www.openbsd.org/faq/upgrade52.patch</b>
<b>patch -C -p0 < upgrade52.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 5.1, 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 <code>sysctl.conf</code>.
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.
<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 nsd.conf, look at the suggested change of strategy, and decide if
it is appropriate for your use).
<blockquote><pre>
etc/bgpd.conf
etc/iked.conf
</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>
</blockquote>
<p><br><p>
<b><i>All upgraders, whether merging via sysmerge(8) or patch file
should continue the upgrade process with these steps:</i></b>
<h3 id="RmFiles">2. Files to delete</h3>
A number of files should be deleted from your system.
Note that some of these may not exist on all systems; that's ok.
Copy and paste the following lines:
<blockquote><pre>
<b>rm /usr/bin/lint
rm /usr/libexec/lint[12]
rm -r /usr/libdata/lint
rm /usr/share/man/man1/lint.1
rm /etc/rc.d/btd
rm /usr/sbin/pkg
rm /sbin/raidctl
rm /usr/share/man/man4/raid.4
rm /usr/share/man/man8/raidctl.8
rm /usr/libexec/tftpd
rm -r /usr/lib/gcc-lib/*-unknown-openbsd5.1</b>
</pre></blockquote>
<h3 id="Kernchk">3. 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 5.1, it is likely you will need to modify the stock kernel of 5.2.
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.
<p>
<h3 id="Pkgup">4. 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>Subversion gnome-keyring is now a subpackage:</b>
gnome-keyring support in Subversion was previously a FLAVOR of the port,
as it required the main program to link with libpthread causing some
side-effects with the previous uthread library (notably, strange
behavior with "svn diff | more" due to how I/O on file descriptors
was handled).
<p>
As this is no longer an issue with rthreads, the FLAVOR has been removed.
To continue using gnome-keyring with Subversion, after updating packages you
will need to "pkg_add gnome-keyring-subversion".
<p>
<li><b>xpdf-utils replaced with poppler-utils:</b>
The PDF-related tools from xpdf-utils (pdffonts, pdfimages, pdfinfo,
pdftotext) have been replaced with equivalents in poppler-utils.
Note that these no longer read xpdfrc files and are now only configured
using command-line options.
<p>
<li><b>ser removed:</b>
The ser port has been removed. Users of ser are advised to migrate
to kamailio for now.
<p>
<li><b>scrotwm renamed to spectrwm:</b>
The package update will be handled automatically but you will need to
rename your configuration files:
<code>mv /etc/scrotwm.conf /etc/spectrwm.conf</code> for the system
configuration file, and any <code>.scrotwm.conf</code> files in user home directories
will need to be renamed to <code>.spectrwm.conf</code>.
You will also need to adapt any entries in <code>.xsession</code>, etc., to start the
window manager.
<p>
<li><b>xxxterm renamed to xombrero:</b>
The package update will be handled automatically but you will need to
rename your configuration files and directories.
There is no system configuration file, but any <code>.xxxterm.conf</code> files in
user home directories will need to be renamed to <code>.xombrero.conf</code>.
<p>
<li><b>dovecot:</b>
Dovecot was updated to 2.1 which may require minor changes to configuration.
See the <a href="https://wiki2.dovecot.org/Upgrading/2.1">upgrade notes</a>
for details.
</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 5.2 packages directory on your CD or nearest FTP mirror,
and use something like
<blockquote><pre>
<b>pkg_add -u</b>
</pre></blockquote>
where the <code>-u</code> indicates update mode;
pkg_add will prompt you for input when it encounters
some ambiguity. Read the
<a href="https://man.openbsd.org/OpenBSD-5.2/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>
<a href="index.html">[FAQ Index]</a> |
<a href="upgrade51.html">[5.0 -> 5.1]</a> |
<a href="upgrade53.html">[5.2 -> 5.3]</a>
<hr>
<small>$OpenBSD: upgrade52.html,v 1.32 2023/04/09 07:14:45 jsg Exp $</small>
![[BACK]](/icons/back.gif){kind=icon}
Return to upgrade52.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www / faq