Saga of an OpenBSD Upgrade - 2.7 to 3.0

Because with Remote Upgrades, slip o' the finger means Road Trip!

This document chronicles the remote upgrade of an OpenBSD firewall box from 2.7 to 3.0.

Major changes from 2.7 to 3.0

This list was compiled by reviewing the upgrade minifaq and my list of detailled /etc changes.

If you're reading this, you'll realize it's quite a bit out of date. You might want to go check out Paul Pruett's upgrade tips.

General Upgrade Steps

Using some of the unallocated space on the drive, configure an /upgrade partition to contain the backups and upgrade files. (The rest of this document assumes that /upgrade exists.) This is a good reason to always leave unallocated space when partioning. For reference, here's my disk layout

  Filesystem  512-blocks     Used    Avail Capacity  Mounted on
  /dev/wd0a       126334    37840    82178    32%    /
  /dev/wd0d       253342        2   240674     0%    /tmp
  /dev/wd0e       594878     8802   556334     2%    /var
  /dev/wd0f      2974554   945728  1880100    33%    /usr
  /dev/wd0h       395902    17372   358736     5%    /home
  /dev/wd0i      3965416        0  3965416     0%    /upgrade

If all goes well, the remote machine will now be happily running 3.1. Of course, if you're using the box as a firewall, you'll have to drop in your new firewall ruleset at this point. Migrating IPF rules to PF, thankfully, is a subject for another day.

Kjell Wooding

(Ahem. This page looks much prettier with a standards-compliant browser. Please see the FAQ.)

pintday.org: We rant so you don’t have to.

pintday.org

Fresh Every Tuesday

Recent Rants

..................
..................
..................
.....|`""""`|.....
.....|# ####|.....
.....# ######.....
.....# ######.....
.....|# ####|.....
.....|# ####|.....
_____|# ####|_____
/////|# ####|/////
//////`""""`//////
//////////////////
//////////////////