<!doctype html>
<html lang=en id=faq>
<title>OpenBSD Upgrade Guide: 4.5 to 4.6</title>
<meta charset=utf-8>
<meta name="description" content="OpenBSD Upgrade Process for 4.5 -> 4.6">
<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/upgrade46.html">
<h2 id=OpenBSD>
<a href="../index.html">
<i>Open</i><b>BSD</b></a>
Upgrade Guide: 4.5 to 4.6
</h2>
<hr>
<p>
<a href="index.html">[FAQ Index]</a> |
<a href="upgrade45.html">[4.4 -> 4.5]</a> |
<a href="upgrade47.html">[4.6 -> 4.7]</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="#newInstaller">NEW INSTALLER!</a>
<li><a href="#newPF">Changes to PF</a>
<li><a href="#newDWM">Changes to daily, weekly, monthly scripts</a>
<li><a href="#newtmux">tmux(1) moved from port to base</a>
<li><a href="#newLynx">lynx updated</a>
<li><a href="#newInstReboot">New install/reboot sequence</a>
<li><a href="#newsysmerge">New sysmerge tool</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.5 and 4.6, 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="../plus46.html">plus46.html</a> and the CVS change logs.
<ul>
<li id="newInstaller"><b>NEW INSTALLER!</b><br>
OpenBSD's traditionally lean and easy to use installer has been improved
and made even leaner and easier to use!
This is not really an upgrade issue, but experienced OpenBSD users will
probably want to look through the new <a href="faq4.html">Installation
Guide</a>.
<p>
<li id="newPF"><b>A number of changes have been made to
<a href="pf/index.html">PF</a>.</b><br>
<i><b>Your existing <code>pf.conf</code> file will probably not work with
4.6 without modifications!</b></i>
If you reboot your system without a usable <code>pf.conf</code> file in
place, your pf rules will not be loaded, and you will end up using the
default rule set, which will block all traffic EXCEPT for ssh over the
standard port 22.
This means that if you do not fix your <code>pf.conf</code> rules before
rebooting, you may be greeted by a box that does not even respond to
pings.
<i>Do not panic</i>, as you can still ssh to the box, assuming you have
sshd(8) listening on the usual port.
<ul>
<li><b>pf is now enabled by default in rc.conf.</b><br>
The default <code>pf.conf</code> <i>file</i> is still quite permissive, but
if that file does not load (and again, it probably won't without
modifications!) a very restrictive rule set will be activated in place
of the one in your <code>pf.conf</code> file, which will permit nothing
other than SSH to the system.
This upgrade process will activate pf by default. If you don't wish
this to happen, add "pf=NO" to your
<a href="faq10.html#rc"><code>/etc/rc.conf.local</code></a>
<li><b>Packet normalization ("scrubbing") has been integrated with the main
ruleset.</b><br>
This is now specified by adding the "scrub (options)" parameter to
rules.
For example:
<blockquote><pre>
scrub in all no-df max-mss 1440
</pre></blockquote>
can be replaced with a rule using the new "match" action:
<blockquote><pre>
match in all scrub (no-df max-mss 1440)
</pre></blockquote>
<li><b>Packet reassembly has been simplified.</b><br>
"Crop" and "drop-ovl" have been removed; only full reassembly remains.
It is now on by default, manually controlled like this:
<blockquote><pre>
set reassemble yes|no [no-df]
</pre></blockquote>
If "no-df" is given, fragments (and only fragments!) with the df bit set
have it cleared before entering the fragment cache, and thus the
reassembled packet doesn't have df set either.
Non-fragmented packets are unaffected by no-df.
<li><b><a href="https://man.openbsd.org/pfctl">pfctl(8)</a>
was changed so that "set require-order" is now disabled by default.</b><br>
This is advisory only, no configuration change is necessary.
</ul>
<p>
<li id="newDWM"><b>Changes to
<a href="https://man.openbsd.org/daily.8">daily(8),
weekly, monthly,</a> and
<a href="https://man.openbsd.org/security.8">security(8)</a>
scripts</b><br>
When updating your periodic maintenance scripts to the latest versions, pay attention to the following changes:
<ul>
<li>The scripts daily, weekly, and monthly now all use the PATH variable
from the root crontab(5), which is <code>/bin:/sbin:/usr/bin:/usr/sbin</code>
by default.
The daily(8) PATH no longer includes <code>/usr/local/bin</code>, the
weekly(8) PATH no longer includes <code>/usr/libexec</code>.
In <code>daily.local</code>, <code>weekly.local</code> and
<code>monthly.local</code>, you can still add additional directories to the
PATH.
<li>All four scripts now suppress section headers when there is no
content to follow.
When a script produces no output whatsoever, it does not send mail to
root any more.
This may require adjustment of your parser scripts.
<li>The security(8) script now uses some shell functions from daily(8),
so it cannot run stand-alone.
Use "<code>sudo /bin/sh /etc/daily</code>" in case you need to run it
manually.
</ul>
<p>
<li id="newtmux"><b><a href="https://man.openbsd.org/tmux.1">tmux(1)</a>
has moved from being a port to being part of the base system.</b><br>
For most users, tmux(1) is a functional replacement for the commonly
installed package, "screen".
It also provides the functionality of the rarely used window(1) command,
which has been removed.
Users of "screen" (and window) are highly encouraged to check it out,
more <a href="faq7.html#tmux">here</a>.
<p>
<li id="newLynx"><b><a href="https://man.openbsd.org/lynx.1">lynx(1)</a>
Has been updated to 2.8.6rel.5.</b><br>
This upgrade process will overwrite your existing <code>/etc/lynx.conf</code>
file, if you have local modifications to it, you will have to reapply
them to the new file.
<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="newsysmerge"><b><a href="https://man.openbsd.org/sysmerge.8">sysmerge(8)</a>
utility:</b><br>
OpenBSD now includes the
<a href="https://man.openbsd.org/sysmerge.8">sysmerge(8)</a>
utility, which helps administrators update configuration files after
upgrading their system.
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>.
For past upgrades, we've presented a list of files that are usually
copied over "as-is", and a list of files which should be changed, and a
patch file that applies those changes to what might be in those files on
your system.
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>
Note that while sysmerge can handle ALL the changes of <code>/etc</code>,
<code>/dev</code>, <code>/root</code> and <code>/var</code>, we highly recommend
that you do some steps manually before hand, as it will save time and
reduce the possibility of user error.
In particular, it is highly recommended that you do not use sysmerge to
update your user and group accounts, as it is very easy to chose the
wrong option leading to erasing your entire user base and setting the
root password to an empty value, preventing remote login to fix the
problem.
<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.6 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.6 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.5, it is likely you will need to modify the stock kernel of 4.6.
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.6 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>OpenBSD/sparc users only:</b><br>
The kernel has grown enough that the sparc boot loader has to be updated
with the new 4.6 boot loader before the system is rebooted, using
<a href="https://man.openbsd.org/OpenBSD-4.6/sparc/installboot">installboot(8)</a>.
These steps should be used at this point to install the new boot code:
<blockquote><pre>
<b>export RELEASEPATH=</b><i>/usr/rel</i> <i># where you put the files</i>
<b>tar -C / -xzphf ${RELEASEPATH}/base46.tgz ./usr/mdec</b>
<b>cp /usr/mdec/boot /</b>
<b>/usr/mdec/installboot -v /boot /usr/mdec/bootxx /dev/rsd0c</b>
</pre></blockquote>
Note: there is no need to do this if running the install kernel, this
only is needed for upgrading a running system remotely.
<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>
(if you are using the multiprocessor kernel, follow up with<br>
<code> <b>cp /bsd /bsd.sp ; mv /bsd.mp /bsd</b></code><br>
afterwards)
<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>etc46.tgz</code> and <code>xetc46.tgz</code> now, because
that will overwrite your current configuration files!</i>
Note that we are installing base46.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 xserv46.tgz</b>
<b>tar -C / -xzphf xfont46.tgz</b>
<b>tar -C / -xzphf xshare46.tgz</b>
<b>tar -C / -xzphf xbase46.tgz</b>
<b>tar -C / -xzphf game46.tgz</b>
<b>tar -C / -xzphf misc46.tgz</b>
<b>tar -C / -xzphf comp46.tgz</b>
<b>tar -C / -xzphf man46.tgz</b>
<b>tar -C / -xzphf base46.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>etc46.tgz</code> and <code>xetc46.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.6/i386/MAKEDEV">MAKEDEV</a>
file was copied to /dev by the installation of
<code>base46.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>
Users need to be added for smtpd(8) and rpc.rwalld(8):
<blockquote><pre>
<b>useradd -u 95 -g =uid -c "SMTP Daemon" -d /var/empty -s /sbin/nologin _smtpd</b>
<b>useradd -u 96 -g =uid -c "rpc.rwalld" -d /var/empty -s /sbin/nologin _rwalld</b>
</pre></blockquote>
<h3 id="etcUpgrade">2. Upgrading <code>/etc</code></h3>
<p>
You will want to extract the <code>etc46.tgz</code> files to a temporary
location:
<blockquote><pre>
<b>export RELEASEPATH=/usr/rel</b>
<b>tar -C /tmp -xzphf ${RELEASEPATH}/etc46.tgz</b>
</pre></blockquote>
Files that can probably be copied from <code>etc46.tgz</code> "as is":
<blockquote><pre>
etc/daily
etc/weekly
etc/monthly
etc/lynx.cfg
etc/rc
etc/rc.conf
etc/security
etc/skel/.Xdefaults
etc/mail/Makefile
etc/mail/smtpd.conf
etc/mailer.conf
etc/mtree/4.4BSD.dist
etc/mtree/special
root/.Xdefaults
</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>etc46.tgz</code> in the above recommended place:
<blockquote><pre>
<b>cd /tmp/etc </b>
<b>cp daily weekly monthly lynx.cfg mailer.conf rc rc.conf security /etc</b>
<b>cp skel/.Xdefaults /etc/skel</b>
<b>cp mtree/4.4BSD.dist mtree/special /etc/mtree</b>
<b>cp ../root/.Xdefaults /root</b>
<b>cp mail/Makefile mail/smtpd.conf /etc/mail</b>
</pre></blockquote>
<p>
<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.6. 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/login.conf
etc/sudoers
etc/sysctl.conf
etc/mail/aliases
etc/skel/.login
etc/skel/.mailrc
root/.login
root/.profile
var/cron/tabs/root
var/www/conf/httpd.conf
</pre></blockquote>
The changes to these files are in <a href="upgrade46.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 < upgrade46.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.5, 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/ntpd.conf
etc/pf.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>
<h3 id="sysmerge">3b. Merging locally changed files via sysmerge(8)</h3>
<p>
The new
<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.6-release</i> or from one <i>-current</i> to a later one.
<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>etc46.tgz</code> and <code>xetc46.tgz</code> files exists in
your $RELEASEPATH, run it with:
<blockquote><pre>
<b>sysmerge -as $RELEASEPATH/etc46.tgz -x $RELEASEPATH/xetc46.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.5, it is likely you will need to modify the stock kernel of 4.6.
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>py-Django:</b> Django 1.0 breaks compatibility with 0.96 in some
areas, as described
<a href="http://docs.djangoproject.com/en/1.0/releases/1.0-porting-guide/">here</a>.
<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.
</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.6 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.6/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="upgrade45.html">[4.4 -> 4.5]</a> |
<a href="upgrade47.html">[4.6 -> 4.7]</a>
<hr>
<small>$OpenBSD: upgrade46.html,v 1.37 2021/03/15 10:18:43 jsg Exp $</small>
![[BACK]](/icons/back.gif){kind=icon}
Return to upgrade46.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www / faq