Language Selection

English French German Italian Portuguese Spanish

FreeBSD 12.1-BETA2 Now Available

Filed under

The second BETA build of the 12.1-RELEASE release cycle is now

Installation images are available for:

o 12.1-BETA2 amd64 GENERIC
o 12.1-BETA2 i386 GENERIC
o 12.1-BETA2 powerpc GENERIC
o 12.1-BETA2 powerpc64 GENERIC64
o 12.1-BETA2 powerpcspe MPC85XXSPE
o 12.1-BETA2 sparc64 GENERIC
o 12.1-BETA2 armv6 RPI-B
o 12.1-BETA2 armv7 BANANAPI
o 12.1-BETA2 armv7 BEAGLEBONE
o 12.1-BETA2 armv7 CUBIEBOARD
o 12.1-BETA2 armv7 CUBIEBOARD2
o 12.1-BETA2 armv7 RPI2
o 12.1-BETA2 armv7 PANDABOARD
o 12.1-BETA2 armv7 WANDBOARD
o 12.1-BETA2 armv7 GENERICSD
o 12.1-BETA2 aarch64 GENERIC
o 12.1-BETA2 aarch64 RPI3
o 12.1-BETA2 aarch64 PINE64
o 12.1-BETA2 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

Installer images and memory stick images are available here:

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-BETA1 includes:

o An off-by-one error in fusefs(5) had been fixed.

o A problem with in-place strip(1) on msdosfs(5) had been fixed.

o Stability fixes for mpr(4) and mps(4) have been merged from head.
  Note, support for these drivers have been removed for 32-bit powerpc.

o A regression had been fixed in the ping6(8) utility when the system is
  built without capsicum(4).

o A regression in the jme(4) driver had been fixed.

o A change to the bhyve(4) uart(4) driver had been fixed to support
  running under syzkaller.

o The WITH_PIE and WITH_BIND_NOW build knobs have been added.

o The 'updatesready' and 'showconfig' subcommands have been added to

o The camcontrol(8) 'devtype' subcommand had been fixed to correctly
  report SATL devices.

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

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):

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:

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-0fde974647f2afb71
  ap-south-1 region: ami-08c5b6c3c67660000
  eu-west-3 region: ami-0d2295cb848b04044
  eu-west-2 region: ami-0defe97a58c32e336
  eu-west-1 region: ami-04794e03ec4994477
  ap-northeast-2 region: ami-0376260338b9a442c
  ap-northeast-1 region: ami-030b542da16e02b36
  sa-east-1 region: ami-09fef4294a171f081
  ca-central-1 region: ami-0444d3dbbb3d973d2
  ap-east-1 region: ami-01870b4cd52cd63f5
  ap-southeast-1 region: ami-0ef470ae9dddc6d31
  ap-southeast-2 region: ami-0eb87756562803e37
  eu-central-1 region: ami-0d4f1151306798937
  us-east-1 region: ami-0aa4feba66441f8cb
  us-east-2 region: ami-073aac094f7a1e753
  us-west-1 region: ami-0b702fd3bc6987d9e
  us-west-2 region: ami-01e70706d53dcbd16

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

  eu-north-1 region: ami-004e595acdaea9f8a
  ap-south-1 region: ami-043ee11f276cbac49
  eu-west-3 region: ami-0a3ca0207e9a78b42
  eu-west-2 region: ami-04cf3e3951b03f0e7
  eu-west-1 region: ami-0846d71aa6ed537a7
  ap-northeast-2 region: ami-0c8b2410ee65152eb
  ap-northeast-1 region: ami-0d0495617fe90c04d
  sa-east-1 region: ami-08f2f3eb468314f2f
  ca-central-1 region: ami-0ea0dff5097085c4f
  ap-east-1 region: ami-0e8e411b892c424f3
  ap-southeast-1 region: ami-0552d07457be8afe7
  ap-southeast-2 region: ami-0f89f9d16dc3fc949
  eu-central-1 region: ami-05f5b271d7603e2cb
  us-east-1 region: ami-0dd2d517058d5c225
  us-east-2 region: ami-06d46829d315d1e20
  us-west-1 region: ami-047a11f3142a87598
  us-west-2 region: ami-0df2f50be88aa4073

=== Vagrant Images ===

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

    % vagrant init freebsd/FreeBSD-12.1-BETA2
    % 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-BETA2

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

	# 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: OpenBSD at EuroBSDcon 2019

More in Tux Machines

Open source technology, enabling innovation

One of the most exciting projects to come out of the open source revolution is Kubernetes, a tool helping companies running their software on cloud services. It enables them to get the most out of the processing power they’re paying for by identifying machines that are being underutilised. So, if the software detects that a machine is not being optimised, it will load it up with another task so it’s working as hard as it can. Read more

Forbes Raves Upcoming Linux Desktop will enclose Windows 10 and macOS

Forbes senior employee Jason Evangelho dedicated an entire article to an upcoming update for a Sino-domestic Linux distribution: If you haven't paid attention to a bit of Linux desktop distribution called Deepin, it's time to put it on your radar. Remember that Huawei Deepin chose to ship on their MateBook laptop lineup. Remember that Deepin Cloud Sync (for system settings) is a great, progressive feature that every Linux distro must use. Remember that the retractable control center from the future looks like something sexy and sensible. But looking at 2020, Deepin is absolutely breathtaking. This is without a doubt the nicest desktop environment I have ever seen … For me, the UX is more intuitive and pleasant than macOS and Windows 10. And luckily a quick setting can also transform Deepin into the traditional Windows or macOS desktop paradigm's that you are already familiar with. Hell, even the installer is a relief. Read more Also: Differences between Windows and Linux operating systems. The fundamental differences that are worth knowing

[libre-riscv-dev] power pc

So as you know, the RISCV Foundation is seriously impeding progress. There
is huge momentum around RISCV itself, however as far as open *innovation*
is concerned, the sheer arrogance of the Foundation in failing to respect
the combination of Libre goals and business objectives has us completely
isolated from key critical resources such as the closed secret lists and

We cannot even get access to documentation explaining how to propose new

I have been considering for some time to reach out to MIPS and PowerPC.
Yesterday I wrote to the OpenPower Foundation and was really surprised and
delighted to hear back from Hugh Blemings, whom I worked with over 20 years

I outlined some conditions (no NDAs, open mailing lists, use of
Certification Marks and Compliance Suites) and he replied back that this
was pretty much along the lines of what they were planning.

I will have a chat with him some time, in the meantime I found the spec:

It is eeenooormous, however Hugh reassures me that they want to break it
into sections.

Why would we even consider this?

The lesson from RISCV is really clear: if the ISA is set up as a cartel,
Libre innovation is not welcome.

If we had a goal to just *implement* a *pre existing* Extension, there
would be no problem.

It is the fact that we wish to implement entirely new extensions, for CPU
and GPU *and* VPU purposes, but not as a separate processor (which would be
classified as "custom") that is the "problem".

So starting at page 1146, we need to work out how to shoe horn a ton of
stuff into the ISA, as well as fit 16 bit compressed in as well.

Read more Also: Libre RISC-V Open-Source Effort Now Looking At POWER Instead Of RISC-V

Calamares grabs onto things

I’ve been working on Calamares, the Universal Linux Installer, for a little over two years – following up in the role Teo started. It’s used by Neon (for the dev version, not the user version) and Manjaro and lots of other Linux distributions. I’ve typically called it an installer for boutique distro’s, as opposed to the Big Five. Well, Debian 11 has plans. And lubuntu uses it as well (and has for over six months). Those seem pretty big. Read more