Language Selection

English French German Italian Portuguese Spanish

FreeBSD 12.1-RC2 Now Available

Filed under
BSD

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

The second RC build of the 12.1-RELEASE release cycle is now available.

Installation images are available for:

o 12.1-RC2 amd64 GENERIC
o 12.1-RC2 i386 GENERIC
o 12.1-RC2 powerpc GENERIC
o 12.1-RC2 powerpc64 GENERIC64
o 12.1-RC2 powerpcspe MPC85XXSPE
o 12.1-RC2 sparc64 GENERIC
o 12.1-RC2 armv6 RPI-B
o 12.1-RC2 armv7 BANANAPI
o 12.1-RC2 armv7 BEAGLEBONE
o 12.1-RC2 armv7 CUBIEBOARD
o 12.1-RC2 armv7 CUBIEBOARD2
o 12.1-RC2 armv7 CUBOX-HUMMINGBOARD
o 12.1-RC2 armv7 RPI2
o 12.1-RC2 armv7 PANDABOARD
o 12.1-RC2 armv7 WANDBOARD
o 12.1-RC2 armv7 GENERICSD
o 12.1-RC2 aarch64 GENERIC
o 12.1-RC2 aarch64 RPI3
o 12.1-RC2 aarch64 PINE64
o 12.1-RC2 aarch64 PINE64-LTS

Note regarding arm SD card images: For convenience for those without
console access to the system, a freebsd user with a password of
freebsd is available by default for ssh(1) access.  Additionally,
the root user password is set to root.  It is strongly recommended
to change the password for both users after gaining access to the
system.

Installer images and memory stick images are available here:

    https://download.freebsd.org/ftp/releases/ISO-IMAGES/12.1/

The image checksums follow at the end of this e-mail.

If you notice problems you can report them through the Bugzilla PR
system or on the -stable mailing list.

If you would like to use SVN to do a source based update of an existing
system, use the "releng/12.1" branch.

A summary of changes since 12.1-RC1 includes:

o The loader.efi had been updated to use ioalign for compliance with
  UEFI specification 2.7A.

o A null pointer dereference bug had been fixed.

o A fix to SCTP to reset local variables to their initial values had
  been added.

o The ixgbe(4) driver had been updated to prevent a system crash when
  configuring EEE on X500EM_X devices.

o The sdhci(4) driver had been updated to fix a boot issue on Beaglebone
  SoCs.

A list of changes since 12.0-RELEASE is available in the releng/12.1
release notes:

    https://www.freebsd.org/releases/12.1R/relnotes.html

Please note, the release notes page is not yet complete, and will be
updated on an ongoing basis as the 12.1-RELEASE cycle progresses.

=== Virtual Machine Disk Images ===

VM disk images are available for the amd64, i386, and aarch64
architectures.  Disk images may be downloaded from the following URL
(or any of the FreeBSD download mirrors):

    https://download.freebsd.org/ftp/releases/VM-IMAGES/12.1-RC2/

The partition layout is:

    ~ 16 kB - freebsd-boot GPT partition type (bootfs GPT label)
    ~ 1 GB  - freebsd-swap GPT partition type (swapfs GPT label)
    ~ 20 GB - freebsd-ufs GPT partition type (rootfs GPT label)

The disk images are available in QCOW2, VHD, VMDK, and raw disk image
formats.  The image download size is approximately 135 MB and 165 MB
respectively (amd64/i386), decompressing to a 21 GB sparse image.

Note regarding arm64/aarch64 virtual machine images: a modified QEMU EFI
loader file is needed for qemu-system-aarch64 to be able to boot the
virtual machine images.  See this page for more information:

    https://wiki.freebsd.org/arm64/QEMU

To boot the VM image, run:

    % qemu-system-aarch64 -m 4096M -cpu cortex-a57 -M virt  \
	-bios QEMU_EFI.fd -serial telnet::4444,server -nographic \
	-drive if=none,file=VMDISK,id=hd0 \
	-device virtio-blk-device,drive=hd0 \
	-device virtio-net-device,netdev=net0 \
	-netdev user,id=net0

Be sure to replace "VMDISK" with the path to the virtual machine image.

=== Amazon EC2 AMI Images ===

FreeBSD/amd64 EC2 AMIs are available in the following regions:

  eu-north-1 region: ami-0186d6a5fbc8766f2
  ap-south-1 region: ami-0b6bef3551f1b0f70
  eu-west-3 region: ami-062495360178ede5e
  eu-west-2 region: ami-0ccfe49c85e5f8cc0
  eu-west-1 region: ami-0e2730782e7462f98
  ap-northeast-2 region: ami-053ddd72fc1feb00a
  ap-northeast-1 region: ami-06cd2e1981334f254
  sa-east-1 region: ami-08acf6b9b1df41f34
  ca-central-1 region: ami-064249d804369c668
  ap-east-1 region: ami-020c406cb2f52030b
  ap-southeast-1 region: ami-08264f040bf980098
  ap-southeast-2 region: ami-0da02f500e46cac8f
  eu-central-1 region: ami-05458e84d05b820e8
  us-east-1 region: ami-06f6cbd134064befb
  us-east-2 region: ami-0cfe92105f4fee6a8
  us-west-1 region: ami-0bb63fac9c5ec153a
  us-west-2 region: ami-00a29b19544968928

FreeBSD/aarch64 EC2 AMIs are available in the following regions:

  eu-north-1 region: ami-0ea4448b9b547107c
  ap-south-1 region: ami-07a9fd713466fe63f
  eu-west-3 region: ami-02e84241865e90f54
  eu-west-2 region: ami-0b707024f9aadb94f
  eu-west-1 region: ami-0abf12b852be4e776
  ap-northeast-2 region: ami-086547036e5a47816
  ap-northeast-1 region: ami-038017fcbf85e7669
  sa-east-1 region: ami-0da52f30dd7d86ef5
  ca-central-1 region: ami-092ee6a89213c15a2
  ap-east-1 region: ami-0db28099cf79bf65d
  ap-southeast-1 region: ami-0852402b94d58adf8
  ap-southeast-2 region: ami-01f869cc877cef54f
  eu-central-1 region: ami-04d008006fdb7e720
  us-east-1 region: ami-0411db3e8715d4352
  us-east-2 region: ami-01e68c35d7ddcac3e
  us-west-1 region: ami-02dcdcd99bf7fde1f
  us-west-2 region: ami-09ce8334b595dff30

=== Vagrant Images ===

FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can
be installed by running:

    % vagrant init freebsd/FreeBSD-12.1-RC2
    % vagrant up

=== Upgrading ===

The freebsd-update(8) utility supports binary upgrades of amd64 and i386
systems running earlier FreeBSD releases.  Systems running earlier
FreeBSD releases can upgrade as follows:

	# freebsd-update upgrade -r 12.1-RC2

During this process, freebsd-update(8) may ask the user to help by
merging some configuration files or by confirming that the automatically
performed merging was done correctly.

	# freebsd-update install

The system must be rebooted with the newly installed kernel before
continuing.

	# shutdown -r now

After rebooting, freebsd-update needs to be run again to install the new
userland components:

	# freebsd-update install

It is recommended to rebuild and install all applications if possible,
especially if upgrading from an earlier FreeBSD release, for example,
FreeBSD 11.x.  Alternatively, the user can install misc/compat11x and
other compatibility libraries, afterwards the system must be rebooted
into the new userland:

	# shutdown -r now

Finally, after rebooting, freebsd-update needs to be run again to remove
stale files:

	# freebsd-update install

Read more

Also: FreeBSD 12.1-RC2 Has Update For UEFI 2.7A, Various Bug Fixes

More in Tux Machines