Re: FreeBSD 13.0-RC3 Now Available
On Mon, Mar 22, 2021 at 01:39:06PM +0100, Goran Mekić wrote: > Hello, > > I see the RC3 in the "Latest News" but not here: > https://www.freebsd.org/releases/13.0R/schedule/ > I hope I'm writing to the proper channels/list about this. > Fixed. Thank you for the report. Glen signature.asc Description: PGP signature
Re: FreeBSD 13.0-RC3 Now Available
Hello, I see the RC3 in the "Latest News" but not here: https://www.freebsd.org/releases/13.0R/schedule/ I hope I'm writing to the proper channels/list about this. Regards, meka signature.asc Description: PGP signature
Re: FreeBSD 13.0-RC3 Now Available
On Sun, 21 Mar 2021 at 03:08, Glen Barber wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > The third RC build of the 13.0-RELEASE release cycle is now available. > > === Upgrading === > > The freebsd-update(8) utility supports binary upgrades of amd64, i386, > and aarch64 systems running earlier FreeBSD releases. Systems running > earlier FreeBSD releases can upgrade as follows: > > # freebsd-update upgrade -r 13.0-RC3 > > 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 Hi, There are two edge cases where the above update instructions will not work. 1) Due to the VLAN re-write in ifconfig(8), if a user is using a host that is fully utilising VLAN tagging, the machine will not be available on the network until the second reboot. The user will either need IPMI/LOM access to the console to execute the second 'freebsd-update install' command or have a way of it being executed and automatically rebooting prior to having access to the host on the network again. 2) If a user has a 12.2 zpool checkpoint in play and booting via BIOS legacy mode, the machine will hang at next reboot with 'zio_read error: 5' 'ZFS: i/o error - all block copies unavailable' 'ZFS: can not read checkpoint data.' The machine will have to be rebooted with a boot ISO and the checkpoint will need to be discarded and the system will boot correctly again (rewind has been unsuccessful). Please note: This does not appear to be an issue where hosts use UEFI for booting operating systems or if zpool checkpoints are destroyed prior to the update process. Cheers, Jason. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 13.0-RC3 Now Available
Hi! > The third RC build of the 13.0-RELEASE release cycle is now available. Upgrading a 13.0-RC2 poudriere jail to RC3 seems to fail ? # poudriere jail -u -j 130 -t 13.0-RC3 [...] To install the downloaded upgrades, run "/usr/sbin/freebsd-update.fixed install". Installing updates...Scanning //usr/share/certs/blacklisted for certificates... Scanning //usr/share/certs/trusted for certificates... done. No updates are available to install. Run '/usr/sbin/freebsd-update.fixed fetch' first. [00:00:42] Error: Fail to upgrade system A second attempt: Fetching metadata signature for 13.0-RC3 from update4.freebsd.org... done. Fetching metadata index... done. Fetching 1 metadata patches. done. Applying metadata patches... done. Fetching 1 metadata files... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 13.0-RC3-p0. touch: f465c3739385890c221dff1a05e578c6cae0d0430e46996d319db7439f884336-install/kernelfirst: No such file or directory To install the downloaded upgrades, run "/usr/sbin/freebsd-update.fixed install". No updates are available to install. Run '/usr/sbin/freebsd-update.fixed fetch' first. [00:01:08] Error: Fail to upgrade system -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD 13.0-RC3 Now Available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The third RC build of the 13.0-RELEASE release cycle is now available. Installation images are available for: o 13.0-RC3 amd64 GENERIC o 13.0-RC3 i386 GENERIC o 13.0-RC3 powerpc GENERIC o 13.0-RC3 powerpc64 GENERIC64 o 13.0-RC3 powerpc64le GENERIC64LE o 13.0-RC3 powerpcspe MPC85XXSPE o 13.0-RC3 armv6 RPI-B o 13.0-RC3 armv7 GENERICSD o 13.0-RC3 aarch64 GENERIC o 13.0-RC3 aarch64 RPI o 13.0-RC3 aarch64 PINE64 o 13.0-RC3 aarch64 PINE64-LTS o 13.0-RC3 aarch64 PINEBOOK o 13.0-RC3 aarch64 ROCK64 o 13.0-RC3 aarch64 ROCKPRO64 o 13.0-RC3 riscv64 GENERIC o 13.0-RC3 riscv64 GENERICSD 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/13.0/ 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 Git to do a source based update of an existing system, use the "releng/13.0" branch. A summary of changes since 13.0-RC2 includes: o A virtual memory list locking fix has been addressed. o A fix for systems running under VirtualBox has been addressed. o A fix in the service(8) utility has been addressed. o The if_wg(4) pseudo driver has been removed. o A fix to TSO for TCP/IPV6 has been addressed in the vtnet(4) driver. o Several other miscellaneous fixes have been addressed. A list of changes since 12.2-RELEASE is available in the releng/13.0 release notes: https://www.freebsd.org/releases/13.0R/relnotes.html Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 13.0-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/13.0-RC3/ 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::,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. BASIC-CI images can be found at: https://download.freebsd.org/ftp/releases/CI-IMAGES/13.0-RC3/ === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are available in the following regions: af-south-1 region: ami-0ad55ef28f5927282 eu-north-1 region: ami-0fde22c6026e95a57 ap-south-1 region: ami-06fd5c64b54c3e005 eu-west-3 region: ami-093ba1f2661abd0be eu-west-2 region: ami-0803205f015f5ec14 eu-south-1 region: ami-03e90955c75a8c809 eu-west-1 region: ami-0d9313767b0b818fd ap-northeast-3 region: ami-0f25c989c843d8dbb ap-northeast-2 region: ami-0f27bdd4fd819bb6c me-south-1 region: ami-032ee25ad2976ad49 ap-northeast-1 region: ami-0fb5829e3ff1f1b15 sa-east-1 region: ami-0f66abb1219e00a5c ca-central-1 region: ami-062381d2a77db4a3d ap-east-1 region: ami-0d21456c4a5bd1384 ap-southeast-1 region: ami-0519190624816cc77 ap-southeast-2 region: ami-0805e040cf3167547 eu-central-1 region: ami-0abb1093896437395 us-east-1 region: ami-02f65312a05a1abfd us-east-2 region: ami-023106328f1d2d3c7 us-west-1 region: ami-00802b96b8eec8b49 us-west-2 region: ami-090a96d68eed457a1 FreeBSD/aarch64 EC2 AMIs are available in the following regions: af-south-1 region: ami-04e1b958484d79c53 eu-north-1 region: ami-09784ab80e6a9812f ap-south-1 region: ami-0641ef56dae855387 eu-west-3 region: ami-0cc83c013292eb9ee eu-west-2 region: ami-033fa6488ab12698b eu-south-1 region: ami-02fe3008ea2757fed eu-west-1 region: ami-06fdd3bce845d8c96 ap-northeast-3 region: ami-0afb61493a8eb593d ap-northeast-2 region: ami-0a81e284ff987ba61 me-south-1 region: ami
