From owner-svn-doc-head@FreeBSD.ORG Fri Jul 18 12:32:16 2014
Return-Path: The so-called "CUSE4BSD" has been imported into the base
system of &os;-11. CUSE is short for character device in
- userspace. The CUSE library is a wrapper for the devfs(8)
+ userspace. The CUSE library is a wrapper for the devfs(8)
kernel functionality which is exposed through /dev/cuse. In
order to function, the CUSE kernel code must either be enabled
in the kernel configuration file or loaded separately as
@@ -166,7 +166,7 @@
There is also ongoing work on improving CTL functionality.
It was already made to support three of four VMware VAAI storage
- acceleration primitives (net/istgt supports 2), while the goal
+ acceleration primitives (net/istgt supports 2), while the goal
is to reach full VAAI support during next months. With all these improvements, and earlier improvements in CAM, GEOM, ZFS,
@@ -608,13 +608,13 @@
added UEFI support to the &os; installer and release image
creation script. The EFI framebuffer requires the vt(4) system console —
+ The EFI framebuffer requires the vt(4) system console —
a framebuffer driver is not implemented for the legacy
- syscons(4) console. Ed added automatic vt(4) selection to the
+ syscons(4) console. Ed added automatic vt(4) selection to the
UEFI boot path. Snapshots are now built as dual-mode images, and should boot
- via BIOS and UEFI. Our plan is to merge the UEFI and vt(4)
+ via BIOS and UEFI. Our plan is to merge the UEFI and vt(4)
work to stable/10 to appear in &os; 10.1-RELEASE.
Work continues on the Foundation-sponsored autofs automount - daemon, UEFI boot support, the updated vt(4) system video + daemon, UEFI boot support, the updated vt(4) system video console, virtual machine images, and the Intel graphics driver update. Foundation-sponsored work resulted in 226 commits to &os; over the April to June period.
@@ -952,7 +952,7 @@ drivers that implement peripheral drivers and SIMs for CAM MMC. The plan is to use a modified version of BeagleBone Black SDHCI controller driver for SIM and a modified version of - mmcsd(4) as a peripheral driver. + mmcsd(4) as a peripheral driver.pkg(8) is the new package management tool for &os;. It +
pkg(8) is the new package management tool for &os;. It is now the only supported package management tool for &os; releases from 10.0-RELEASE, including the upcoming - 9.3-RELEASE. pkg(8) is available on all currently supported + 9.3-RELEASE. pkg(8) is available on all currently supported releases. Support for the legacy pkg_tools is due to be discontinued at the beginning of September 2014.
-The release of pkg(8) 1.3 is imminent. This includes major +
The release of pkg(8) 1.3 is imminent. This includes major improvements in the dependency solver. Now we can:
There are plans to use pkg(8) to package up the base system. +
There are plans to use pkg(8) to package up the base system. Along with other benefits, this will allow writing a universal installer: download one installer image and from there install any available version of &os;, including snapshots.
-We are also intending to use pkg(8) within the ports tree at +
We are also intending to use pkg(8) within the ports tree at package-build time to handle fulfilling build dependencies. This opens the possibility of installing build-dependencies by downloading binary packages, which means you can install @@ -1209,7 +1209,7 @@
We were generally short on time this quarter. We made less progress than expected on all fronts.
-The alternate pkg(8) repository, built with WITH_NEW_XORG, is +
The alternate pkg(8) repository, built with WITH_NEW_XORG, is now available. This alleviates the need for users to rebuild their ports with WITH_NEW_XORG. See the announcement, linked above for further information.
@@ -1302,7 +1302,7 @@ -Extensive testing of tmpfs(5) using the stress2 kernel test +
Extensive testing of tmpfs(5) using the stress2 kernel test suite was done. The issues found were debugged and fixed.
Most of the problems are related to the bugs in the