Monday, October 14, 2013

FreeBSD 10.0-BETA1 now available

FreeBSD 10.0-BETA1 now available

The first beta build of the 10.0-RELEASE release cycle is now available for the amd64, i386, ia64, powerpc, powerpc64 and sparc64 architectures.  ISO images and, for architectures that support it, memory stick images are available here.

Preinstalled virtual machine images are available for the amd64 and i386 architectures, located under the 'snapshots' directory here.  The disk images are available in both QCOW2 and VMDK format.  The image download size is approximately 136 MB, which decompress to a 20GB sparse image.

The image checksums can be found in the announcement.

If you notice problems you can report them through the PR system or on the -current or -stable mailing lists.

If you would like to use SVN to do a source based update of an existing system, use the "stable/10" branch.

Important note to freebsd-update(8) users:  Due to a last minute problem found in the 10.0-BETA1 freebsd-update(8) builds, freebsd-update(8) is NOT supported for 10.0-BETA1 upgrades.  Please do not use freebsd-update(8) to upgrade to 10.0-BETA1.

Also note, due to the size of the images, the ports.txz distribution is not included in 10.0-BETA1, however is expected to be included with disc1.iso for subsequent builds during the release cycle.

The ports tree can be fetched either with the portsnap(8) utility, or using svnlite using any of the mirrors listed here.

Changes between -ALPHA5 and -BETA1 include:

  • Introduce freebsd-version(1), which is intended to be used as an auditing tool, to determine the userland patch level when it differs from what 'uname -r' reports.
  • Improve ZFS lzjb decompress performance.
  • Add two new MIPS CPU families - mips24k and mips74k.
  • The "jail_<jname>_*" rc.conf(5) variables for per-jail configuration are automatically converted to /var/run/jail.<jname>.conf before the jail(8) utility is invoked, so the new jail.conf(5) syntax is used.
  • Remove most of the ATF tools and the _atf user.
  • Updates to random(4).
    • In 10.0-BETA1, it is not possible for random(4) to be loaded as a kernel module via kldload(8).  If not using GENERIC, and the system kernel configuration excludes 'device random', please include random(4) in the kernel configuration file.  The fix for this issue is pending review, and is expected to be fixed in 10.0-BETA2.
  • Updates to bsdinstall(8).
    • 10.0-BETA1 introduces a number of updates to bsdinstall(8), notably the ability to install to a full ZFS filesystem.  Please keep in mind that this is an experimental feature.
    • If using the ZFS installation option in and have enabled full-disk encryption is enabled, a few entries will need to be manually added to loader.conf(5) before the 'bootpool' zpool will be available after the system boots.  This manual step is expected to be fixed in 10.0-BETA2.
      • The entries that need to be added are:
        • zpool_cache_load="YES"
        • zpool_cache_type="/boot/zfs/zpool.cache"
        • zpool_cache_name="/boot/zfs/zpool.cache"
      • This can be done at the final menu of bsdinstall(8), when prompted to boot into the newly-installed system; alternatively, this can be done post-install, in which case, the following must be run before appending loader.conf(5):
        • # zpool import -f bootpool