The developers of FreeBSD have made available version 10.2-RC2. Follow the newsletter link to see the whole list of changes and full details.
The second RC build of the 10.2-RELEASE release cycle is now available. Installation images are available for: o amd64 GENERIC o i386 GENERIC o ia64 GENERIC o powerpc GENERIC o powerpc64 GENERIC64 o sparc64 GENERIC The image checksums follow at the end of this email. FreeBSD/arm SD card images are available for: o BEAGLEBONE o CUBOX-HUMMINGBOARD o GUMSTIX o RPI-B o PANDABOARD o WANDBOARD Note: For convenience for those without console access to supported arm devices, a default 'freebsd' user exists for ssh(1) login. The password is 'freebsd', which it is strongly recommended to change after gaining access to the system. Additionally, the 'root' user password is 'root', which is also recommended to change. All images can be downloaded from: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.2/
If you notice problems, please report them through the Bugzilla PR system. If you would like to use SVN to do a source based update of an existing system, use the "releng/10.2" branch. A list of changes since 10.1-RELEASE are available in the release notes: https://www.freebsd.org/releases/10.2R/relnotes.html Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 10.2-RELEASE cycle progresses. === Changes Since 10.2-RC1 === o The pkg(8) repository configuration file used to populate the /packages directory on the dvd1.iso for amd64 and i386 has been corrected to use the 'quarterly' branch for RC2. o ntpd(8) has been updated to use a static build date for reproducibility, as well as no longer links against libmd. o The nvme(4) driver has been updated to fix an issue where ZFS TRIM on pool initialization would appear to hang the system, with several additional updates. o An issue where the UEFI loader would create an invalid device path has been fixed. o A bug in the pre-8.x F_GETLK command for fcntl(2) emulation of advisory locks was fixed. o A shell injection vulnerability in patch(1) has been fixed. [FreeBSD-SA-15:14] o An issue with TCP reassembly leading to mbuf(9) exhaustion has been fixed. [FreeBSD-SA-15:15] o OpenSSH has been updated to address multiple vulnerabilities. [FreeBSD-SA-15:16] o A regression related to suspend and resume for several laptops has been fixed. o Several issues have been fixed in pf(4). o The VHD-formatted virtual machine disk images have changed to use the fixed-size format instead of the dynamic-size format. o An issue related to UDP checksum offloading has been fixed for Hyper-V on Windows Server 2012 and earlier. o A locking issue that could cause FreeBSD/sparc64 systems to panic has been fixed. o An issue in the uart(4) driver that could trigger a system panic has been fixed. o tar(1) has been updated to address an issue when compressing sparse files. o The pms(4) driver for PMC Sierra SAS/SATA HBA controllers has been removed from the GENERIC kernel configuration. In order to use the driver, add pmspcv_load="YES" to loader.conf(5) or at the loader(8) prompt, run 'load pmspcv.ko'. Note, there is an issue with the driver where it will attempt to attach to controllers it should not. At present, a post-release Errata Notice is planned for this issue, to allow time for the issue to be properly resolved in 11-CURRENT and 10-STABLE. === 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): ftp://ftp.freebsd.org/pub/FreeBSD/releases/VM-IMAGES/10.2-RC2/ The partition layout is: ~ 512k - freebsd-boot GPT partition type (bootfs GPT label) ~ 1GB - freebsd-swap GPT partition type (swapfs GPT label) ~ ~17GB - 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, which decompress to a 20GB sparse image. Note to consumers of the dvd1.iso image: The bsdconfig(8) utility cannot install the packages included on the DVD, however they can be installed manually. To install packages from the dvd1.iso image, create and mount the /dist directory: # mkdir -p /dist # mount -t cd9660 /dev/cd0 /dist Replace '/dev/cd0' with the appropriate cd(4) device as necessary. Next, bootstrap pkg(8) from the DVD: # env REPOS_DIR=/dist/packages/repos \ pkg bootstrap At this point, pkg-install(8) can be used to install additional packages from the DVD. Please note, the REPOS_DIR environment variable should be used each time using the DVD as the package repository, otherwise conflicts with packages from the upstream mirrors may occur when they are fetched. For example, to install Gnome and Xorg, run: # env REPOS_DIR=/dist/packages/repos \ pkg install xorg-server xorg gnome3 [...] === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are available in the following regions: us-east-1 region: ami-9ff355f4 us-west-1 region: ami-1b1be75f us-west-2 region: ami-bb68618b sa-east-1 region: ami-5b199746 eu-west-1 region: ami-9cd98eeb eu-central-1 region: ami-e00206fd ap-northeast-1 region: ami-2ac5782a ap-southeast-1 region: ami-82515dd0 ap-southeast-2 region: ami-b12b6b8b === Azure / VM Depot Images === FreeBSD/amd64 images are available for use within the Microsoft Azure hosting platform through VM Depot. For deployment instructions, see: https://vmdepot.msopentech.com/Vhd/Show?vhdId=56718&version=59090 === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site for the VMWare Desktop and VirtualBox providers, and can be installed by running: % vagrant init freebsd/FreeBSD-10.2-RC2 % 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 10.2-RC2 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 9.x. Alternatively, the user can install misc/compat9x 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 Regards, Glen Love FreeBSD? Support this and future releases with a donation to the FreeBSD Foundation! https://www.freebsdfoundation.org/donate/