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 any changes must be made to the kernel, the safest thing to do is to make those changes on a local 5.1 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.
Also, the use of the Open BSD ksh(1) shell is assumed.
Stop any appropriate applications: During this process, all the userland applications will be replaced but may not be runnable, and strange things may happen as a result.
Table of Contents: This is not a complete list of the changes that took place between 5.0 and 5.1, 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 plus51and the CVS change logs.Upgrading is a convenient way to bring your Open BSD system up to the most recent version.However, the results are not intended to precisely match the results of a wipe-and-reload installation.Save a copy of reboot(8), install new userland applications.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.Using sysmerge(8) for the first time: If you have a system that's been upgraded in the past via the patchfile process you will probably find the FIRST time you upgrade by sysmerge, you have a LOT of manual file changes to make.