FreeBSD 12.1-RC1 Now Available

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
The first RC build of the 12.1-RELEASE release cycle is now available.
Installation images are available for:
o 12.1-RC1 amd64 GENERIC
o 12.1-RC1 i386 GENERIC
o 12.1-RC1 powerpc GENERIC
o 12.1-RC1 powerpc64 GENERIC64
o 12.1-RC1 powerpcspe MPC85XXSPE
o 12.1-RC1 sparc64 GENERIC
o 12.1-RC1 armv6 RPI-B
o 12.1-RC1 armv7 BANANAPI
o 12.1-RC1 armv7 BEAGLEBONE
o 12.1-RC1 armv7 CUBIEBOARD
o 12.1-RC1 armv7 CUBIEBOARD2
o 12.1-RC1 armv7 CUBOX-HUMMINGBOARD
o 12.1-RC1 armv7 RPI2
o 12.1-RC1 armv7 PANDABOARD
o 12.1-RC1 armv7 WANDBOARD
o 12.1-RC1 armv7 GENERICSD
o 12.1-RC1 aarch64 GENERIC
o 12.1-RC1 aarch64 RPI3
o 12.1-RC1 aarch64 PINE64
o 12.1-RC1 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-BETA3 includes:
o A NULL pointer dereference that could lead to a system crash had been
fixed.
o A fix to correctly implement pmap_page_is_mapped() on arm64 and riscv.
o A fix to tun(4) and tap(4) when destroying interfaces had been added.
o A fix to krping to notify sleeping threads of device removal had been
added.
o Several updates to mlx5core, mlx5en(4), and mlx5ib(4).
o Several fixes in libusb(3) and xhci(4) have been added.
o Several SCTP and TCP fixes have been added.
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-RC1/
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-0c2caa354f54dcc8e
ap-south-1 region: ami-011f6d0b22b4179ae
eu-west-3 region: ami-0e633b1e66b94dc5e
eu-west-2 region: ami-06f77908c8875b5ce
eu-west-1 region: ami-07d5b3d4ffa682d66
ap-northeast-2 region: ami-0a0d9969831c99d3f
ap-northeast-1 region: ami-092398d1a41a67f27
sa-east-1 region: ami-023dd6db41165f441
ca-central-1 region: ami-0cf9fd10259cf4eb2
ap-east-1 region: ami-0e255d1bb4a1f76f4
ap-southeast-1 region: ami-0404212cff3236606
ap-southeast-2 region: ami-0fea81c67debcba8b
eu-central-1 region: ami-08e32f4e90fd250f4
us-east-1 region: ami-0e6e401d0ffebd916
us-east-2 region: ami-0d094195cae5bf901
us-west-1 region: ami-04c1e10d06064e68d
us-west-2 region: ami-02d0010139a9a494e
FreeBSD/aarch64 EC2 AMIs are available in the following regions:
eu-north-1 region: ami-022e4644320e82ac1
ap-south-1 region: ami-0e421a1864d53d226
eu-west-3 region: ami-0bffb1c264a4b8d09
eu-west-2 region: ami-0f596a538918dc9c8
eu-west-1 region: ami-063c017d8b9086b55
ap-northeast-2 region: ami-0b34ed283d7dd41ae
ap-northeast-1 region: ami-0071602b3e78a8de0
sa-east-1 region: ami-07986820662819e67
ca-central-1 region: ami-0d9ee49739059957b
ap-east-1 region: ami-00ae1e2b897eb6230
ap-southeast-1 region: ami-0018127ce245410e0
ap-southeast-2 region: ami-02fa0380052cd268f
eu-central-1 region: ami-01836dc7a9f273243
us-east-1 region: ami-0018654c0af06d99d
us-east-2 region: ami-06a4203b93836b927
us-west-1 region: ami-09c5010072b44bd96
us-west-2 region: ami-063fae5c2ec327807
=== Vagrant Images ===
FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can
be installed by running:
% vagrant init freebsd/FreeBSD-12.1-RC1
% 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-RC1
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
-

- Login or register to post comments
Printer-friendly version- 2743 reads
PDF version
More in Tux Machines
- Highlights
- Front Page
- Latest Headlines
- Archive
- Recent comments
- All-Time Popular Stories
- Hot Topics
- New Members
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.
|
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.
|
today's howtos
|








.svg_.png)
Content (where original) is available under CC-BY-SA, copyrighted by original author/s.

Article by Michael Larabel in Phoronix
FreeBSD 12.1 Is Near With Libomp Finally In Base, LLD Linker By Default For i386