FreeBSD 11.1-BETA3 Now Available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The third BETA build of the 11.1-RELEASE release cycle is now available. Installation images are available for: o 11.1-BETA3 amd64 GENERIC o 11.1-BETA3 i386 GENERIC o 11.1-BETA3 powerpc GENERIC o 11.1-BETA3 powerpc64 GENERIC64 o 11.1-BETA3 sparc64 GENERIC o 11.1-BETA3 armv6 BANANAPI o 11.1-BETA3 armv6 BEAGLEBONE o 11.1-BETA3 armv6 CUBIEBOARD o 11.1-BETA3 armv6 CUBIEBOARD2 o 11.1-BETA3 armv6 CUBOX-HUMMINGBOARD o 11.1-BETA3 armv6 GUMSTIX o 11.1-BETA3 armv6 RPI-B o 11.1-BETA3 armv6 RPI2 o 11.1-BETA3 armv6 PANDABOARD o 11.1-BETA3 armv6 WANDBOARD o 11.1-BETA3 aarch64 GENERIC Note regarding arm/armv6 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/11.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 "stable/11" branch. A summary of changes since BETA2 includes: o The mlx4en(4) driver has been updated to use static device numbering instead of dynamic numbering. o The patch(1) utility has been updated to fix an infinite loop when failing to read the specified input. o The bsdinstall(8) utility has been updated to use consistent EFI partition configuration across all supported platforms. o A system panic when booting a single CPU system has been corrected. o The vmxnet3(4) driver has been updated to fix a system crash when LRO (large receive offloading) was enabled. o An issue where an ethernet adapter would not report "no carrier" after disconnecting the network cable has been corrected. o The qlnxe(4) driver firmware has been updated to version 8.30.0.0. A list of changes since 11.1-RELEASE are available in the stable/11 release notes: https://www.freebsd.org/relnotes/11-STABLE/relnotes/article.html Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 11.1-RELEASE cycle progresses. === Virtual Machine Disk Images === VM disk images are available for the amd64 and i386 architectures. Disk images may be downloaded from the following URL (or any of the FreeBSD FTP mirrors): https://download.freebsd.org/ftp/releases/VM-IMAGES/11.1-BETA3/ 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. === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are available in the following regions: ap-south-1 region: ami-99255bf6 eu-west-2 region: ami-60150304 eu-west-1 region: ami-a08299c6 ap-northeast-2 region: ami-fb1cc395 ap-northeast-1 region: ami-92d3c4f5 sa-east-1 region: ami-42d8b32e ca-central-1 region: ami-3fa9165b ap-southeast-1 region: ami-76911e15 ap-southeast-2 region: ami-c79383a4 eu-central-1 region: ami-c1b117ae us-east-1 region: ami-02c0ea14 us-east-2 region: ami-1979587c us-west-1 region: ami-607e5200 us-west-2 region: ami-cef4e0b7 === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site, and can be installed by running: % vagrant init freebsd/FreeBSD-11.1-BETA3 % 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 11.1-BETA3 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 reboo
Re: FreeBSD 11.1-BETA3 Now Available
excerpt from Glen Barber's announcement: > A list of changes since 11.1-RELEASE are available in the stable/11 > release notes: > https://www.freebsd.org/relnotes/11-STABLE/relnotes/article.html > Please note, the release notes page is not yet complete, and will be > updated on an ongoing basis as the 11.1-RELEASE cycle progresses. Changes since 11.1-RELEASE, not out yet? You must have meant 11.0-RELEASE. I went to that web site for the release notes and looked especially at the Network Drivers section. Nothing about re(4) which is not working for me in 11.1-BETA2 (as well as HEAD). It worked for a time on HEAD sometime prior to 11.0-RELEASE and also on stable/10 for a time. My stable/10 installations no longer exist, having been updated to stable/11. I even filed a bug (219625, also 219626), believe 219625 is the one on re(4) (MSI Z77 MPOWER motherboard). Tom ___ 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 11.1-BETA3 Now Available
On Sat, Jun 24, 2017 at 09:18:26PM +, Thomas Mueller wrote: > excerpt from Glen Barber's announcement: > > > A list of changes since 11.1-RELEASE are available in the stable/11 > > release notes: probably meant 11.1-BETA2 ? mcl ___ 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"
lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work
The following is based mostly on an extraction from a private exchange in which a question was asked and my answer was unsettling: incompatibilities within the 11.* family. I would not normally send to re but doing so was explicitly mentioned. Hopefully this example is reasonable for doing that. Aspect #0: what is broken currently (and in the future?) within the 11.* family? lang/gcc* packages built on release/11.0.1/ to not work fully on stable/11/ or on the drafts of release/11.1.0/ . (I leave releng/11.*/'s implicit.) -r313194 in head and was describied with: > Define the vm_ooffset_t and vm_pindex_t types as machine-independend. > > The types are for the byte offset and page index in vm object. They > are similar to off_t, which is defined as 64bit MI integer. Using MI > definitions will allow to provide consistent MD values of vm > object-related maximum sizes. The known issue is the generation of header dependencies in the lang/gcc* builds on release/11.0.1/ that when used on stable/11/ or release/11.0.1/ generate reports like: /usr/local/lib/gcc5/gcc/x86_64-portbld-freebsd11.0/5.4.0/include-fixed/sys/types.h:266:9: error: '__vm_ooffset_t' does not name a type typedef __vm_ooffset_t vm_ooffset_t; ^ /usr/local/lib/gcc5/gcc/x86_64-portbld-freebsd11.0/5.4.0/include-fixed/sys/types.h:268:9: error: '__vm_pindex_t' does not name a type typedef __vm_pindex_t vm_pindex_t; ^ *** [CoinFactorization2.lo] Error code 1 Unfortunately UPDATING was not updated for head/'s -r313194 (2017-Feb-4) --nor for stable/11/'s -r313574 (2017-Feb-11), the MFC. (No MFC was made to stable/10/ or to release/10.3.0 as far as I found.) (These changes predate the INO64 issue in head/ . Head ends up with more issues than I'm dealing with here.) Aspect #1: what 11.* version builds the pre-built packages targeting 11.* and the apparent consequences (given the vm_ooffset_t and vm_pindex_t changes and the lang/gcc* build behavior) This is the unsettling part for pre-built packages: incompatibilities within the 11.* family for the lang/gcc* packages. http://portsmon.freebsd.org/portoverview.py?category=%3Bamng&portname=gcc5&wildcard= shows categories for builds for 8.4 9.3 10.1 10.3 11.0 head (Nothing for stable/*/ .) But the 10.3 rows show no package builds. I would guess that they start once 10.1 stops (approximately). So it may be that 11.1 will not get package builds until 11.0 stops (approximately). If so unless lang/gcc* are changed to bootstrap differently they will configure to match release/11.0.1/ and will not be compatible with the vm_ooffset_t and vm_pindex_t changes in stable/11/ and release/11.1.0/ . But as I understand updating how the lang/gcc* builds work to remove such dependencies is under investigation. I do not know any timing relative to release/11.1.0/ if my understanding is right. Until then (if I was right): Unless there are separate packages made for targeting release/11.0.1/ vs. release/11.1.0/ it is not obvious when lang/gcc* packages will be generally compatible with various folks choices about what to install as the system version within the release/11.*/ and stable/11/ family. This would likely be true even if they were built on release/11.1.0/ : then release/11.0.1/ likely would have compatibility problems. The ABI versioning does not cover the specific issues involved based on how vm_ooffset_t and vm_pindex_t were changed and what the lang/gcc* builds do relative to such changes. Yet there is incompatibility for some fairly-significant-usage ports. Aspect #2: stable/10/ and release/10.4.0/ Just covered for completeness: I do not see a MFC of -r313194 to stable/10/ : its sys/sys/types.h dates back to 2015-Oct-10. So it looks like 10.x has a permanent difference in this area: 10.x continues to get separate lang/gcc* package builds from 11.x and later. No problem for this context as far as I know. Note: To simplify I choose to not be explicit about what authors wrote what original text. If that becomes an issue, it is correctable. Blame me for any errors in the above. === Mark Millard markmi at dsl-only.net ___ 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"
