[OpenBSD]

[FAQ Index]

Following -current

Table of Contents

Introduction

This document is for people who wish to follow -current. It contains information about changes from 4.6-release to -current, and should NOT be used by anyone upgrading from 4.5 or earlier, or people wishing to follow -stable.

If you wish to update to 4.6-release or 4.6-stable from previous versions, see the upgrade guide.

Make sure you have read and understood FAQ 5 - Building the System from Source before using -current and the instructions below.

You should ALWAYS use a snapshot as the starting point for running -current. Upgrading by compiling your own source code is not supported.

If you wish to see upgrade information for earlier versions of OpenBSD, see upgrade-old.html. This is provided as a historical record -- it should NOT be used as an upgrade procedure guide.

2009/07/21 - [ports] New postgresql version

The new version of postgresql requires that your databases be dumped before upgrade and reloaded after.

2009/07/24 - thread model posix enabled for gcc 3

This change was reverted. No special steps are needed now.

2009/07/25 - audio and MIDI device naming change

sndio(7) now uses a different scheme for audio and MIDI device naming. Though the old naming will continue working for some time, it's recommended to start updating any scripts or configuration files of applications using sndio(7), as follows:

2009/07/26 - thread model posix reverted for gcc 3

For users who upgraded userland to enable thread model posix for gcc3, follow these steps to upgrade. Otherwise no special steps are needed.

2009/08/01 - "split-horizon" default behaviour and syntax change in ripd(8)

2009/08/18 - sysmerge(8) default running mode change

sysmerge(8) now runs in auto-mode by default.
The "-a" switch has been replaced by "-b" which can be used to get the former behaviour (full diff mode).

2009/08/26 - ftp(1) auto-fetch redirection handling change

In ftp(1), when auto-fetching (command line operation) is used without specifying a filename with -o, the file is now always saved under a filename derived from the command line. Previous behaviour was to derive the filename from the redirection URL.

2009/09/01 - pf(4) address translation changes

As described in more detail in this mailing list post, PF's separate nat/rdr/binat (translation) rules have been replaced with actions on regular match/filter rules. Simple rulesets may be converted like this:

   nat on $ext_if from 10/8 -> ($ext_if)
   rdr on $ext_if to ($ext_if) -> 1.2.3.4
becomes
   match out on $ext_if from 10/8 nat-to ($ext_if)
   match in on $ext_if to ($ext_if) rdr-to 1.2.3.4

and... 

   binat on $ext_if from $web_serv_int to any -> $web_serv_ext
becomes
   match on $ext_if from $web_serv_int to any binat-to $web_serv_ext
nat-anchor and/or rdr-anchor lines, e.g. for relayd(8), ftp-proxy(8) and tftp-proxy(8), are no longer used and should be removed from pf.conf(5), leaving only the anchor lines. Translation rules relating to these and spamd(8) will need to be adjusted as appropriate.

N.B.: Previously, translation rules had "stop at first match" behaviour, with binat being evaluated first, followed by nat/rdr depending on direction of the packet. Now the filter rules are subject to the usual "last match" behaviour, so care must be taken with rule ordering when converting.

2009/09/02 - pf(4) route-to/reply-to syntax change

The route-to, reply-to, dup-to and fastroute options in pf.conf move to filteropts; 
   pass in on $ext_if route-to (em1 192.168.1.1) from 10.1.1.1
   pass in on $ext_if reply-to (em1 192.168.1.1) to 10.1.1.1
becomes
   pass in on $ext_if from 10.1.1.1 route-to (em1 192.168.1.1)
   pass in on $ext_if to 10.1.1.1 reply-to (em1 192.168.1.1)

2009/09/04 - bgpd(8), dvmrpd(8) additonal syntax checking

bgpd(8) and dvmrpd(8) now strictly check whether something other than yes or no is used in a yes/no token. If your existing syntax is incorrect (e.g. using "announce capabilities none" instead of "no") this will produce an error at startup rather than starting up and silently giving incorrect behaviour.

2009/10/01 - [ports] Bacula major version update

Bacula has been upgraded from 2.4.4 to 3.0.2; this has a new catalog format which requires a database schema change on the director. The commit log entry and release notes have more details. The server components (storage daemons and director) are not compatible between major versions so these must be upgraded together.

2009/10/06 - bgpd(8) capability announcement changes

bgpd(8) now announces 4-byte ASN and graceful restart capabilities by default. Previously graceful restart was not announced by default, and 4-byte ASN support was only advertised when one or other peer used an ASN above 65535. There is now per-session control over which capabilities are announced: 
   announce refresh yes # was already on by default
   announce restart no
   announce as-4byte no # was only set on sessions to peers with 4byte AS nums

2009/10/19 - need new config(8) to build the kernel

config(8) has been changed. You must install a new version before building a kernel from newly updated sources. 
   # cd /usr/src/usr.sbin/config
   # make
   # make install

2009/10/21 - two packages come with perl 5.10.1

p5-parent and p5-Parse-CPAN-Meta now come with base Perl. If you have installed the packages, delete them. 
   # pkg_delete p5-parent p5-Parse-CPAN-Meta

2009/10/25 - iwn(4) requires a firmware package update

iwn(4) now needs iwn-firmware package version 5.2. You can install the iwn-firmware-5.2 package with: 
   # pkg_add http://damien.bergamini.free.fr/packages/openbsd/iwn-firmware-5.2.tgz

2009/11/03 - pflogd(8) requires new method of logfile rotation

pflogd(8) has lost its -p option. Change /etc/newsyslog.conf to include: 
   /var/log/pflog	600  3     250  *     ZB "pkill -HUP -u root -U root -t - -x pflogd"
[back] www@openbsd.org
$OpenBSD: current.html,v 1.186 2009/11/09 09:37:01 otto Exp $