>>> Updating repositories metadata... 
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
>>> Unlocking package pfSense-kernel-pfSense... done.
>>> Downloading upgrade packages...
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Checking for upgrades (5 candidates): ..... done
Processing candidates (5 candidates): ..... done
The following 5 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	pfSense-repo-devel: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
	pfSense-rc: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
	pfSense-kernel-pfSense: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
	pfSense-default-config: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
	pfSense-base: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]

The process will require 19 KiB more space.
41 MiB to be downloaded.
Fetching pfSense-repo-devel-2.3.b.20160129.1948.txz: . done
Fetching pfSense-rc-2.3.b.20160129.1948.txz: . done
Fetching pfSense-kernel-pfSense-2.3.b.20160129.1948.txz: .......... done
Fetching pfSense-default-config-2.3.b.20160129.1948.txz: . done
Fetching pfSense-base-2.3.b.20160129.1948.txz: .......... done
Checking integrity... done (0 conflicting)
>>> Upgrading pfSense kernel... 
Updating pfSense-core repository catalogue...
pfSense-core repository is up-to-date.
Updating pfSense repository catalogue...
pfSense repository is up-to-date.
All repositories are up-to-date.
Checking integrity... done (0 conflicting)
The following 2 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	pfSense-kernel-pfSense: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
	pfSense-rc: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]

The process will require 1 B more space.
[1/2] Upgrading pfSense-rc from 2.3.b.20160129.1031 to 2.3.b.20160129.1948...
[1/2] Extracting pfSense-rc-2.3.b.20160129.1948: . done
[2/2] Upgrading pfSense-kernel-pfSense from 2.3.b.20160129.1031 to 2.3.b.20160129.1948...
===> Keeping a copy of current kernel in /boot/kernel.old
[2/2] Extracting pfSense-kernel-pfSense-2.3.b.20160129.1948: .......... done
Upgrade is complete.  Rebooting in 10 seconds.
>>> Locking package pfSense-kernel-pfSense... done.
__RC=0 __REBOOT_AFTER=10
Upgrading necessary packages...
Updating pfSense-core repository catalogue...
pkg: http://beta.pfsense.org/packages/pfSense_master_amd64_amd64-core/meta.txz: No address record
repository pfSense-core has no meta file, using default settings
pkg: http://beta.pfsense.org/packages/pfSense_master_amd64_amd64-core/packagesite.txz: No address record
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: http://beta.pfsense.org/packages/pfSense_master_amd64_amd64-pfSense_master/meta.txz: No address record
repository pfSense has no meta file, using default settings
pkg: http://beta.pfsense.org/packages/pfSense_master_amd64_amd64-pfSense_master/packagesite.txz: No address record
Unable to update repository pfSense
All repositories are up-to-date.
Checking for upgrades (3 candidates): ... done
Processing candidates (3 candidates): ... done

pfSense-kernel-pfSense-2.3.b.20160129.1948 is locked and may not be modified
Checking integrity... done (0 conflicting)
The following 3 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
	pfSense-repo-devel: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
	pfSense-default-config: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]
	pfSense-base: 2.3.b.20160129.1031 -> 2.3.b.20160129.1948 [pfSense-core]

The process will require 19 KiB more space.
[1/3] Upgrading pfSense-repo-devel from 2.3.b.20160129.1031 to 2.3.b.20160129.1948...
[1/3] Extracting pfSense-repo-devel-2.3.b.20160129.1948: . done
[2/3] Upgrading pfSense-default-config from 2.3.b.20160129.1031 to 2.3.b.20160129.1948...
[2/3] Extracting pfSense-default-config-2.3.b.20160129.1948: . done
[3/3] Upgrading pfSense-base from 2.3.b.20160129.1031 to 2.3.b.20160129.1948...
===> Keeping a copy of current version mtree
[3/3] Extracting pfSense-base-2.3.b.20160129.1948: .. done
===> Removing schg flag from base files
===> Extracting new base tarball
===> Removing static obsoleted files
>>> Removing unnecessary packages... done.
>>> Cleanup pkg cache... done.