Language Selection

English French German Italian Portuguese Spanish

FreeBSD 12.1-BETA2 Now Available

Submitted by Roy Schestowitz on Sunday 29th of September 2019 02:40:50 AM Filed under
BSD

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

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 CUBOX-HUMMINGBOARD
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
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-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
  freebsd-update(8).

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:

    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-BETA2/

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

»

More in Tux Machines

digiKam 7.7.0 is released

After three months of active maintenance and another bug triage, the digiKam team is proud to present version 7.7.0 of its open source digital photo manager. See below the list of most important features coming with this release. Read more

Dilution and Misuse of the "Linux" Brand

Samsung, Red Hat to Work on Linux Drivers for Future Tech

The metaverse is expected to uproot system design as we know it, and Samsung is one of many hardware vendors re-imagining data center infrastructure in preparation for a parallel 3D world. Samsung is working on new memory technologies that provide faster bandwidth inside hardware for data to travel between CPUs, storage and other computing resources. The company also announced it was partnering with Red Hat to ensure these technologies have Linux compatibility. Read more

today's howtos

  • How to install go1.19beta on Ubuntu 22.04 – NextGenTips

    In this tutorial, we are going to explore how to install go on Ubuntu 22.04 Golang is an open-source programming language that is easy to learn and use. It is built-in concurrency and has a robust standard library. It is reliable, builds fast, and efficient software that scales fast. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel-type systems enable flexible and modular program constructions. Go compiles quickly to machine code and has the convenience of garbage collection and the power of run-time reflection. In this guide, we are going to learn how to install golang 1.19beta on Ubuntu 22.04. Go 1.19beta1 is not yet released. There is so much work in progress with all the documentation.

  • molecule test: failed to connect to bus in systemd container - openQA bites

    Ansible Molecule is a project to help you test your ansible roles. I’m using molecule for automatically testing the ansible roles of geekoops.

  • How To Install MongoDB on AlmaLinux 9 - idroot

    In this tutorial, we will show you how to install MongoDB on AlmaLinux 9. For those of you who didn’t know, MongoDB is a high-performance, highly scalable document-oriented NoSQL database. Unlike in SQL databases where data is stored in rows and columns inside tables, in MongoDB, data is structured in JSON-like format inside records which are referred to as documents. The open-source attribute of MongoDB as a database software makes it an ideal candidate for almost any database-related project. This article assumes you have at least basic knowledge of Linux, know how to use the shell, and most importantly, you host your site on your own VPS. The installation is quite simple and assumes you are running in the root account, if not you may need to add ‘sudo‘ to the commands to get root privileges. I will show you the step-by-step installation of the MongoDB NoSQL database on AlmaLinux 9. You can follow the same instructions for CentOS and Rocky Linux.

  • An introduction (and how-to) to Plugin Loader for the Steam Deck. - Invidious
  • Self-host a Ghost Blog With Traefik

    Ghost is a very popular open-source content management system. Started as an alternative to WordPress and it went on to become an alternative to Substack by focusing on membership and newsletter. The creators of Ghost offer managed Pro hosting but it may not fit everyone's budget. Alternatively, you can self-host it on your own cloud servers. On Linux handbook, we already have a guide on deploying Ghost with Docker in a reverse proxy setup. Instead of Ngnix reverse proxy, you can also use another software called Traefik with Docker. It is a popular open-source cloud-native application proxy, API Gateway, Edge-router, and more. I use Traefik to secure my websites using an SSL certificate obtained from Let's Encrypt. Once deployed, Traefik can automatically manage your certificates and their renewals. In this tutorial, I'll share the necessary steps for deploying a Ghost blog with Docker and Traefik.

More on Tux Machines: About ● Gallery ● Forum ● Blogs ● Search ● News ● RSS Feed

Part of Bytes Media ● Sister sites below.

TechBytes Techrights button

Powered by Drupal, an open source content management system

Content available under CC-BY-SA CC

© by original authors

Powered by CentOS 6.5 (GNU/Linux), Varnish, and Drupal 6