Active OpenBSD development is known as the -current branch. These sources are frequently compiled into releases known as snapshots.
Aggressive changes are sometimes pushed in this branch, and complications can arise when building the latest code or upgrading from a previous point in time. Some of the steps for getting over these hurdles are explained on this page. Make sure you've read and understand how to build the system from source before using -current and the instructions below.
In general, it's far easier to use snapshots, as developers will have gone through much of the trouble for you already.
You should always use a snapshot as the starting point for running
-current.
This process typically consists of running
sysupgrade(8) with the
-s flag.
Alternatively, download (and verify) the appropriate
bsd.rd file from the /snapshots/
directory of your preferred mirror, boot from it,
and choose (U)pgrade at the prompt.
Any installed packages should then be
upgraded after booting into the new system.
Upgrading to -current by compiling your own source code is discouraged for everyone except for experts, as difficult build-time crossing-points can occur often, and no assistance will be provided. In case of failure, use a snapshot to recover.
Most of these changes will have to be performed as root.
AUDIODEVICE environment variable),
then the descriptors might need to be updated as follows.
Otherwise, skip this section.
Audio devices exposed by sndiod(8) are not bound to physical audio devices anymore, so the physical audio device number component of sndio(7) descriptors was removed. For instance, if the server is started with:
# sndiod -f rsnd/0 -s foo -f rsnd/1 -s barthen programs will need to use
"snd/foo" and "snd/bar" (instead of
"snd/0.foo" and "snd/1.bar").
By default programs will try to use "snd/default" (instead
of "snd/0").
Unless -s default option is used,
"snd/default" is automatically created and attached to
the first physical audio device specified on the command line (i.e. first
-f or -F option).
If needed, this setting may be changed at run-time with the
server.device control exposed by
sndioctl(1).
For each physical device managed by the server (i.e. each -f
or -F option) the server also exposes a
"snd/<number>"
descriptor bound to the physical device of the same number.
Consequently, "snd/0", "snd/1", ...
still can be used to refer to specific physical devices.
xterm*allowMouseOps: true