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.
# userdel _switchd # groupdel _switchd # rm /etc/rc.d/switchd /usr/sbin/switchctl /usr/sbin/switchd \ /usr/share/man/man4/switch.4 /usr/share/man/man5/switchd.conf.5 \ /usr/share/man/man8/switchctl.8 /usr/share/man/man8/switchd.8
Before updating, stop slapd and use slapcat to dump your database(s) to ldif files. (Saving ldif files is recommended as part of your regular maintenance anyway, but particularly important at this time).
Adjust the backend database in your configuration to use mdb instead of bdb/hdb. If you are using the old-style /etc/openldap/slapd.conf config file this is relatively straightforward. If you are using upstream's recommended on-line configuration ("cn=config") this is normally edited "in-band" via LDAP, but you might find it difficult to make this type of change in the usual way. Instead you can export to ldif with slapcat -n 0, edit the exported file, then reload with slapadd -n 0. Do not edit the ldif files in /etc/openldap/slapd.d directly.
Regarding the actual changes you need to make: in the simplest case you just need to change "bdb" to "mdb". slapd-bdb(5) has various tuning options which are not used by slapd-mdb(5) (for example, cachesize) - these will need to be removed. For more information, consult the upstream documentation.
After restarting with the updated configuration, you will need to reload your database from the ldif file using slapadd (or if you are updating a read-only replica you could let syncrepl pick it up).
# sed -i 's/\${rcexec}/rc_exec/' /etc/rc.d/myscript
If you find the changes unwelcome, the OpenBSD package includes a copy of the old colour schemes under the legacy subdirectory to make it easier to revert if desired. You can use the subdirectory directly in colorscheme in your configuration, but as these are not included as standard in upstream Vim, if you share config files between various machines you may like to copy the relevant files from /usr/local/share/vim/vim82/colors/legacy to ~/.vim/colors which take priority.
For CangJie / ShuangPin / WuBi / ErBi / ZiRanMa, install fcitx-chinese-addons.
For ZhengMa / Boshiamy / Quick and other WuBi / CangJie tables, install fcitx-table-extra.
export XMODIFIERS=@im=fcitx export GTK_IM_MODULE=fcitx export QT_IM_MODULE=fcitx /usr/local/bin/fcitx5 &
filter-pf-addresses yes in your config, it should be
changed to blocklist pfTblAddrTable.
defaults write sogod WOPort 127.0.0.1:20000