File: [local] / www / faq / upgrade43.html (download) (as text)
Revision 1.34, Tue May 28 01:53:11 2019 UTC (5 years ago) by bentley
Branch: MAIN
CVS Tags: HEAD
Changes since 1.33: +2 -2 lines
Give FAQ pages their own HTML id, for future use.
|
<!doctype html>
<html lang=en id=faq>
<title>OpenBSD Upgrade Guide: 4.2 to 4.3</title>
<meta charset=utf-8>
<meta name="description" content="OpenBSD Upgrade Process for 4.2 -> 4.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/upgrade43.html">
<h2 id=OpenBSD>
<a href="../index.html">
<i>Open</i><b>BSD</b></a>
Upgrade Guide: 4.2 to 4.3
</h2>
<hr>
<p>
<a href="index.html">[FAQ Index]</a> |
<a href="upgrade42.html">[4.1 -> 4.2]</a> |
<a href="upgrade44.html">[4.3 -> 4.4]</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="#libexpat">libexpat has moved to base43.tgz</a>
<li><a href="#httpd.conf">httpd.conf change</a>
<li><a href="#relayd">hoststated(8) renamed to relayd(8)</a>
<li><a href="#carp">carp(4) changes</a>
<li><a href="#xenocaramove">xenocara default tree location changed</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="#Kernchk">Checking the kernel</a>
<li><a href="#Pkgup">Upgrading packages</a>
<li><a href="#rmxbase42">Removing xbase42.tgz</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.2 and 4.3, 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="../plus43.html">plus43.html</a> and the CVS change logs.
<ul>
<li id="libexpat"><b>libexpat has been moved to base43.tgz</b><br>
For 4.2, libexpat moved from ports to xbase42.tgz, which was highly
inconvenient for people who did not have any other reason to install X.
For 4.3, libexpat has moved from xbase42.tgz to base43.tgz, so for many
applications, there is no longer reason to install xbase43.tgz.
<p>
This can create a small problem if you installed xbase42.tgz to get
libexpat on your 4.2 system.
Since you installed xbase42.tgz, you should either remove it or upgrade
it.
If libexpat was the only reason you had xbase42.tgz installed, removing
the old files is probably the best solution.
Details on removing xbase42.tgz are <a href="#rmxbase42">provided</a>.
<p>
Also note that building ports is still only supported with a full
installation, including <i>all</i> X file sets.
<p>
<li id="httpd.conf"><b>httpd.conf change:</b><br>
<a href="faq15.html">Packages</a> for
<a href="https://man.openbsd.org/httpd.8">httpd(8)</a>
modules now install configuration files in
<code>/var/www/conf/modules.samples</code>, and direct the user to create
symbolic links in <code>/var/www/conf/modules</code>.
The following lines should be added to <code>/var/www/conf/httpd.conf</code>
after the <code>LoadModule</code> directives (towards the end of section 1):
<blockquote><pre>
#
# Include extra module configuration files
#
Include /var/www/conf/modules/*.conf
</pre></blockquote>
This is in the <code>upgrade43.patch</code> file, but may not apply properly
to highly customized <code>httpd.conf</code> files.
You should make sure these lines end up in your system, otherwise future
package additions may not work properly after install.
<p>
<li id="relayd"><b>hoststated(8) renamed to relayd(8):</b><br>
<a href="https://man.openbsd.org/OpenBSD-4.2/hoststated">hoststated(8)</a>
has been renamed to
<a href="https://man.openbsd.org/relayd.8">relayd(8)</a>.
This will require a renaming of the <code>_hoststated</code> user and group
to <code>_relayd</code>, plus changes to your <code>/etc/pf.conf</code> file
and a minor rework of your
<a href="https://man.openbsd.org/OpenBSD-4.2/hoststated.conf">hoststated.conf(5)</a>
into a
<a href="https://man.openbsd.org/relayd.conf.5">relayd.conf(5)</a>
file.
The upgrade instructions here will install a new <code>relayd.conf</code>
file, you will need to configure it as you need.
<p>
<li id="carp"><b>carp(4) changes:</b><br>
<a href="https://man.openbsd.org/carp.4">carp(4)</a>
has been changed to make it easier to configure.
If you are running
<a href="https://man.openbsd.org/carp.4">carp(4)</a> with ARP or IP balancing
your configuration needs to be changed accordingly:
<ul>
<li> Multiple carp(4) interfaces sharing an IP have been replaced with
the <code>carpnodes</code> option.
<li> The <code>net.inet.carp.arpbalance</code>
<a href="https://man.openbsd.org/sysctl.8">sysctl(8)</a>
has been replaced with balancing mode <code>arp</code>.
<li> The <code>link0, link1</code>, and <code>link2</code> flags used for IP
balancing have been replaced with the balancing modes
<code>ip, ip-stealth</code> and <code>ip-unicast</code>.
</ul>
<p>
<li id="xenocaramove"><b>xenocara default tree location changed:</b><br>
The default location of the xenocara (<a href="faq11.html">X</a>) source
tree is now <code>/usr/xenocara</code>.
This is important for those who <a href="faq5.html#Xbld">build X from
source</a>.
Simply move your xenocara tree:
<blockquote><pre>
# <b>mv /usr/src/xenocara /usr</b>
</pre></blockquote>
<p>
<li id="rc.conf"><b>rc.conf:</b><br>
Unlike earlier versions of this process, since
<a href="upgrade41.html">4.1</a> 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.3 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>.
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.3 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 "insecure" applications from starting at boot:</b>
There will be a time when PF will be unlikely to be running during this
upgrade process, but your applications may still start and run properly.
Any application dependent upon PF for security should be disabled
before this happens, and should not be re-enabled until proper PF
operation is verified after upgrade.
There may be other applications which you wish to keep from running
during 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.2, it is likely you will need to modify the stock kernel of 4.3.
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.3 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 considering to recompile your kernel.
<p>
<li><b>Install new kernel(s)</b>
<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 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>Install new <code>/etc/firmware</code> files:</b>
Due to the fact that some uploaded "firmware" files may have been updated,
you may need to update the files in the <code>/etc/firmware</code> directory.
This will impact users of only a few devices, though all users can use
this step without harm.
To extract the firmware files from <code>base43.tgz</code>, use the
following as root:
<blockquote><pre>
<b>cd /</b>
<b>tar -C / -xzphf ${RELEASEPATH}/base43.tgz ./etc/firmware</b>
</pre></blockquote>
<p>
<li><b>Install new <code>/sbin/ifconfig</code> utility:</b>
Sometimes the network drivers (especially more complex devices such as
<code>pppoe(4)</code>) in the new kernel need an updated <code>ifconfig</code>
utility to be configured properly after the reboot in the next step.
Again, it's something that all users can do without harm, but if you are
performing your remote upgrade over a <code>pppoe(4)</code> connection this
step can be crucial.
To extract the <code>ifconfig</code> utility from <code>base43.tgz</code>, use the
following as root:
<blockquote><pre>
<b>tar -C / -xzphf ${RELEASEPATH}/base43.tgz ./sbin/ifconfig</b>
</pre></blockquote>
<p>
<li><b>Reboot on the new kernel:</b>
This might be a tempting step to skip, but it should be done now, as
usually, the new kernel will run old userland apps (such as the soon to
be important <code>reboot</code>!), but often a new userland will NOT
work on the old kernel.
<p>
<li><b>Install new userland applications.</b>
<i>Do NOT install <code>etc43.tgz</code> and <code>xetc43.tgz</code> now, because
that will overwrite your current configuration files!</i>
<blockquote><pre>
<b>export RELEASEPATH=</b><i>/usr/rel</i>
<b>cd ${RELEASEPATH}</b>
<b>tar -C / -xzphf base43.tgz</b>
<b>tar -C / -xzphf comp43.tgz</b>
<b>tar -C / -xzphf game43.tgz</b>
<b>tar -C / -xzphf man43.tgz</b>
<b>tar -C / -xzphf misc43.tgz</b>
<b>tar -C / -xzphf xbase43.tgz</b>
<b>tar -C / -xzphf xfont43.tgz</b>
<b>tar -C / -xzphf xserv43.tgz</b>
<b>tar -C / -xzphf xshare43.tgz</b>
</pre></blockquote>
Note: 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>
Note: the files in <code>/etc</code> are handled separately below, so
<code>etc43.tgz</code> and <code>xetc43.tgz</code> are NOT unpacked here.
<p>
<li><b>Upgrade <code>/dev</code>.</b>
The new
<a href="https://man.openbsd.org/OpenBSD-4.3/i386/MAKEDEV">MAKEDEV</a>
file will be copied to /dev by the installation of
<code>base43.tgz</code>, so you simply need to do the following:
<blockquote><pre>
<b>cd /dev</b>
<b>./MAKEDEV all</b>
</pre></blockquote>
<p>
<li><b>Upgrade <code>/etc</code> as below</b>.
<p>
<li><b>Reboot</b>
</ul>
During this process,
<a href="https://man.openbsd.org/sendmail.8">sendmail(8)</a>
may produce some error messages like the following:
<pre>
Nov 1 12:47:05 puffy sm-mta[16733]: filesys_update failed: No such file or directory, fs=., avail=-1, blocksize=380204
</pre>
These messages can be safely ignored for the moment, or you may wish to
halt sendmail(8) during the upgrade process.
Note that sendmail is not working properly at this point, and will need
to be restarted (as part of the reboot) before mail is expected to be
handled properly.
<p>
<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 and changed Users and Groups</h3>
New users are needed for
<a href="https://man.openbsd.org/ospfd.8">ospf6d</a>,
and
<a href="https://man.openbsd.org/snmpd.8">snmpd</a>.
Create those users and groups using
<a href="https://man.openbsd.org/useradd.8">useradd(8)</a>
<blockquote><pre>
<b>useradd -u90 -g=uid -c"OSPF6 Daemon" -d/var/empty -s/sbin/nologin _ospf6d
useradd -u91 -g=uid -c"SNMP Daemon" -d/var/empty -s/sbin/nologin _snmpd</b>
</pre></blockquote>
You also need to use
<a href="https://man.openbsd.org/vipw.8">vipw(8)</a>
to edit the password files and your favorite editor to change the
<code>/etc/group</code> file, changing <code>_hoststated</code> to
<code>_relayd</code> in each, and changing the description in vipw(8) from
"HostState Daemon" to "Relay Daemon".
Leave the rest of each line unchanged.
<h3 id="etcUpgrade">2. Upgrading <code>/etc</code></h3>
<p>
You will want to extract the <code>etc43.tgz</code> files to a temporary
location:
<blockquote><pre>
<b>tar -C /tmp -xzphf ${RELEASEPATH}/etc43.tgz</b>
</pre></blockquote>
Files that can probably be copied from <code>etc43.tgz</code> "as is":
<blockquote><pre>
etc/mail/README
etc/moduli
etc/mtree/4.4BSD.dist
etc/mtree/BSD.local.dist
etc/mtree/special
etc/netstart
etc/ospf6d.conf
etc/rc
etc/rc.conf
etc/relayd.conf
etc/security
etc/snmpd.conf
var/named/etc/root.hint
</pre></blockquote>
Note that it IS possible to locally modify these files, if this has been
done, manual merging will be needed.
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>etc43.tgz</code> in the above recommended place:
<blockquote><pre>
<b>cd /tmp/etc
cp moduli netstart ospf6d.conf rc rc.conf relayd.conf security snmpd.conf /etc
cp mtree/* /etc/mtree/
cp mail/README /etc/mail
cp ../var/named/etc/root.hint /var/named/etc</b>
</pre></blockquote>
<p id="patchfile">
These files likely have local changes, but should be updated for
4.3. IF you have not altered these files, you can copy over the
new version, otherwise the changes must be merged with your files:
<blockquote><pre>
etc/changelist
etc/chio.conf
etc/ftpusers
etc/mail/aliases
etc/ssh/sshd_config
etc/sudoers
etc/sysctl.conf
var/named/etc/named-dual.conf
var/named/etc/named-simple.conf
var/named/etc/named.conf
var/www/conf/httpd.conf
var/www/conf/mime.types
var/www/htdocs/manual/mod/core.html
var/www/htdocs/manual/server-wide.html
</pre></blockquote>
The changes to these files are in <a href="upgrade43.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 < upgrade43.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.2, 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>
<b><code>/etc/ttys</code></b> has been made more consistent across
platforms, but this makes updating more exciting for this file.
It is recommended that you copy over this new file, and manually
merge any changes back to the new one:
<blockquote><pre>
<b>mv /etc/ttys /etc/ttys.orig
cp /tmp/etc/ttys /etc</b>
</pre></blockquote>
<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/pf.conf
</pre></blockquote>
<p>
There are a couple files that can be deleted that are no longer used
in 4.3:
<blockquote><pre>
<b>rm /etc/hoststated.conf /var/named/standard/root.hint</b>
</pre></blockquote>
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>
to create any new directories, and change the ownership and access to
<code>/etc/chio.conf</code>:
<blockquote><pre>
<b>newaliases</b>
<b>mtree -qdef /etc/mtree/4.4BSD.dist -p / -u</b>
<b>chown root:operator /etc/chio.conf</b>
<b>chmod 644 /etc/chio.conf</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 4.2, it is likely you will need to modify the stock kernel of 4.3.
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">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 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.3 packages directory on your CD or nearest FTP mirror,
and use something like
<blockquote><pre>
#<b> pkg_add -ui -F update -F 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.3/pkg_add">pkg_add(1)</a>
manual page and the <a href="faq15.html">package management</a>
chapter of the FAQ for more information.
<h3 id="rmxbase42">5. Removing xbase42.tgz</h3>
If you installed <code>xbase42.tgz</code> to get libexpat installed for
packages that needed it, you no longer need it for 4.3.
You can either remove it or install <code>xbase43.tgz</code>.
<p>
If you wish to remove it, you can use the following commands:
<blockquote><pre>
# <b>mv /usr/X11R6/lib/libexpat.so.* /usr/lib</b>
# <b>rm -r /usr/X11R6 /etc/X11 /etc/fonts</b>
</pre></blockquote>
<p>
If you wish to install <code>xbase43.tgz</code>, then you must clean
the old libexpat files:
<blockquote><pre>
# <b>mv /usr/X11R6/lib/libexpat.so.* /usr/lib</b>
# <b>rm /usr/X11R6/lib/libexpat*</b>
# <b>rm /usr/X11R6/include/expat*</b>
</pre></blockquote>
<p>
<a href="index.html">[FAQ Index]</a> |
<a href="upgrade42.html">[4.1 -> 4.2]</a> |
<a href="upgrade44.html">[4.3 -> 4.4]</a>
<hr>
<small>$OpenBSD: upgrade43.html,v 1.34 2019/05/28 01:53:11 bentley Exp $</small>
![[BACK]](/icons/back.gif){kind=icon}
Return to upgrade43.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www / faq