From owner-svn-doc-all@FreeBSD.ORG Thu Apr 17 17:22:59 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9DA429CB; Thu, 17 Apr 2014 17:22:59 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8972D19F7; Thu, 17 Apr 2014 17:22:59 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s3HHMx31055580; Thu, 17 Apr 2014 17:22:59 GMT (envelope-from pgj@svn.freebsd.org) Received: (from pgj@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s3HHMxSd055579; Thu, 17 Apr 2014 17:22:59 GMT (envelope-from pgj@svn.freebsd.org) Message-Id: <201404171722.s3HHMxSd055579@svn.freebsd.org> From: Gabor Pali Date: Thu, 17 Apr 2014 17:22:59 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44594 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2014 17:22:59 -0000 Author: pgj Date: Thu Apr 17 17:22:59 2014 New Revision: 44594 URL: http://svnweb.freebsd.org/changeset/doc/44594 Log: - Further improvements to the 2014Q1 status report Submitted by: bjk (most of them) Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml Thu Apr 17 17:05:53 2014 (r44593) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2014-01-2014-03.xml Thu Apr 17 17:22:59 2014 (r44594) @@ -212,12 +212,12 @@ definitions and explanations of the terms and features of ZFS.

The remaining section is the FAQ. To help users address the - most common problems they might run into with ZFS. It would - be useful to hear experiences, questions, misconceptions, - gotchas, stumbling blocks, and suggestions for the FAQ section - from other users. Also, a use cases section that highlights - some of the cases where ZFS provides advantages over +

The remaining section is the FAQ, to help users address the + most common problems they might run into with ZFS. It would be + useful to hear experiences, questions, misconceptions, gotchas, + stumbling blocks, and suggestions for the FAQ section from other + users. Also, it would be good to have a use cases section that + highlights some of the cases where ZFS provides advantages over traditional file systems.

Please send suggestions to the freebsd-doc mailing @@ -296,10 +296,10 @@

The &os; Documentation Engineering Team is responsible for - defining and following up documentation goals for the - committers in the Documentation project. The team is pleased - to announce a new member — &a.wblock;. In early March, - the &os; Documentation Engineering Team members assumed + defining and following up on the documentation goals for the + committers in the Documentation project. The team is pleased to + announce a new member — &a.wblock;. In early March, the + &os; Documentation Engineering Team members assumed responsibility for the &os; Webmaster Team.

@@ -342,10 +342,10 @@ currently at its most recent upstream version.

For non-Windows-based Ada development, &os; and DragonFly are - now undisputed as the go-to platforms. The other candidates - are Debian and Fedora, but there are few Ada software on those - platforms that are not also in the &os; ports tree, but the - versions are much older. The Ports Collection also features + now undisputed as the go-to platforms. The other candidates are + Debian and Fedora, but there are few Ada softwares on those + platforms that are not also in the &os; ports tree, and the &os; + versions are much newer. The Ports Collection also features software not found anywhere else such as the USAFA's Ironsides DNS server, libsparkcrypto, matreshka, GNATDroid (Android cross-compiler) and several developer libraries.

@@ -407,7 +407,7 @@

We also follow development of core components (available in - your repository). See link for documentation on how to + your repository). See the links for documentation on how to upgrade those libraries.

Simplify and improve Kyua HTML reports. In particular, reports will be coalesced into single HTML files for easier management and will include more useful details for debugging. - Such details are the revision at which the system was built, - date and duration of the whole run, or list of installed + Such details are the revision at which the system was built, the + date and duration of the whole run, or the list of installed packages, to mention a few examples.

Add JUnit XML output to Kyua for better integration with @@ -689,15 +689,15 @@ -

Arm64 is the name of the in-progress port of &os; to the - ARMv8 CPU when it is in AArch64 mode. Until recently, all ARM - CPU designs were 32-bit only. With the introduction of the - ARMv8, architecture ARM has added a new 64-bit mode. This new - mode has been named AArch64.

Arm64 is the name of the in-progress port of &os; to the ARMv8 + CPU when it is in AArch64 mode. Until recently, all ARM CPU + designs were 32-bit only. With the introduction of the ARMv8 + architecture, ARM has added a new 64-bit mode. This new mode + has been named AArch64.

Progress has been good on getting &os; to build and run on the ARM Foundation model. &os; is able to be built for this - architecture, however it requires a number of external tools + architecture, however, it requires a number of external tools including objdump(1) and ld(1). These tools are provided by an external copy of binutils until replacements can be written.

@@ -871,7 +871,7 @@ Shawn has access to a Raspberry Pi (RPI). PIE is 90% broken. Debug and fix major issues on the RPI. The existing NX stack protections are not obeyed on RPI. Properly - implemented ASLR requires NX stack. + implemented ASLR requires a NX stack.

Shawn will be receiving a sparc64 box on April 6, 2014. He will test ASLR on sparc64, identifying and @@ -881,9 +881,9 @@ Linuxulator. He will be looking into that and fixing those.

Shawn will be cleaning up code and adding more - applications in base to support PIE. He will also add PIE - support to the ports framework for general consumption.

Shawn will be cleaning up code and adding support for PIE to + more applications in base. He will also add PIE support to the + ports framework for general consumption.

Shawn will be giving a presentation regarding ASLR at BSDCan 2014.

Chromebook is an ARMv7 Cortex-A15 personal computer powered - by Samsung Exynos 5 Dual System-on-Chip. As of the current - status of this project, such laptops can be booted with &os; - from USB flash — it works stably (including SMP) and it - can build third-party applications. The display and keyboard - work.

One model of Chromebook is an ARMv7 Cortex-A15 personal + computer powered by a Samsung Exynos 5 Dual System-on-Chip. As of + the current status of this project, such laptops can be booted + with &os; from USB flash — it works stably (including SMP) + and it can build third-party applications. The display and + keyboard work.

Thanks to &a.grehan; for providing hardware.

The project is now in head, stable/10 and stable/9 branches. Hence, vt(4) can be - tested by using VT kernel configuration + tested by using the VT kernel configuration (i386 and amd64) or by replacing two lines in the GENERIC kernel configuration file:

Create sub-directories for vt(4) under /usr/share/ to store key maps and fonts.

Implement remaining features supported by + Implement the remaining features supported by vidcontrol(1). Write the vt(4) manual page. (This is in @@ -1529,7 +1529,7 @@ device vt_efifb

OpenStack is a cloud operating system that controls large pools of compute, storage, and networking resources in a data center. OpenContrail is a network virtualization (SDN) - solution comprising network controller, virtual router and + solution comprising a network controller, virtual router, and analytics engine, which can be integrated with cloud orchestration systems like OpenStack or CloudStack.

@@ -1718,10 +1718,10 @@ device vt_efifb &os;. The second was auditdistd(8) improvements for the &os; cluster.

Work continued on these Foundation-sponsored projects: - Intel graphics driver update by &a.kib;, UEFI boot support for +

Work continued on these Foundation-sponsored projects: Intel + graphics driver update by &a.kib;, UEFI boot support for amd64 by &a.emaste;, autofs automounter and in-kernel - iSCSI stack enhancements, bug fixes by &a.trasz;, updated + iSCSI stack enhancements and bug fixes by &a.trasz;, and updated vt(4) system console by &a.ray;. A more detailed project update for each of the above projects can be found within this quarterly status report.

@@ -1761,9 +1761,9 @@ device vt_efifb

After finishing the 10.0-RELEASE, Foundation system administrator and release engineer &a.gjb; began work on adding support for &os;/arm image builds as part of the - release build process. As result of this work, &os;/arm + release build process. As a result of this work, &os;/arm images are produced as part of the weekly development snapshot - builds, and available from any of the &os; FTP mirrors. + builds, and are available from any of the &os; FTP mirrors. Supported kernel configurations currently include BEAGLEBONE, RPI-B, PANDABOARD, WANDBOARD-QUAD, and ZEDBOARD.

@@ -1797,18 +1797,18 @@ device vt_efifb -

LLDB is the debugger project associated with - Clang/LLVM. It supports Mac OS X, Linux, and &os; platforms, - with ongoing work on Windows. It builds on existing - components in the larger LLVM project, for example using - Clang's expression parser and LLVM's disassembler.

LLDB is the debugger project associated with Clang/LLVM. It + supports the Mac OS X, Linux, and &os; platforms, with ongoing + work on Windows. It builds on existing components in the larger + LLVM project, for example using Clang's expression parser and + LLVM's disassembler.

The majority of work since the last status update has been on bugfixes and implementation of the remaining functionality - missing on &os;. Most of these improvements are now in the - LLDB snapshot in the base system, which has been updated to - upstream Subversion revision r202189. Some highlights of the - new update include:

+ missing on &os;. Most of these improvements are now in the LLDB + snapshot in the base system, which has been updated to upstream + Subversion revision r202189. Some highlights of the new update + include:

Improvements to the remote GDB protocol client.

SDIO card detection and initialization already work, most +

SDIO card detection and initialization already work; most needed bus methods are implemented and tested.

The WiFi driver is able to load firmware onto the card and @@ -2105,53 +2105,51 @@ device vt_efifb Now both the 9.x and 10.x branches share the same support for Intel and AMD GPUs.

The next big tasks are the updates of the DRM generic code - and the i915 driver. Both are making good progress - and the DRM update should hopefully be ready for wider testing - during April. An update of the Radeon driver is on the to-do - list, but nothing is scheduled yet.

The next big tasks are the updates of the DRM generic code and + the i915 driver. Both are making good progress and the + DRM update should hopefully be ready for wider testing during + April. An update of the Radeon driver is on the to-do list, but + nothing is scheduled yet.

On the ports tree and packages side, the update to Cairo 1.12 - mentioned in the last quarterly report is ready to be - committed, as people who tested it either reported - improvements or no regressions. As a reminder, the switch - from Cairo 1.10 to 1.12 causes display artifacts with - xf86-video-intel 2.7.1, but fixes similar problems with other - hardware/driver combinations. Furthermore, Cairo 1.12 is - required by Pango 1.36.0, GTK+ 3.10 and Firefox 27.0. A - Heads up mail will be posted to the + mentioned in the last quarterly report is ready to be committed, + as people who tested it either reported improvements or no + regressions. As a reminder, the switch from Cairo 1.10 to 1.12 + causes display artifacts with xf86-video-intel 2.7.1, but fixes + similar problems with other hardware/driver combinations. + Furthermore, Cairo 1.12 is required by Pango 1.36.0, GTK+ 3.10 + and Firefox 27.0. A Heads up mail will be posted to the freebsd-x11 mailing-list when this update goes live.

In the graphics stack's ports development tree, new Mesa - ports are being worked on. Those ports are required to - support GLAMOR (the GL-based 2D acceleration library used by - Radeon HD 7000+ cards for instance) and OpenCL (using the GPU - to perform non-graphical calculations). We were able to - execute some "Hello World" OpenCL programs and play with - OpenCL in darktable, but there are some compatibility issues - between Clover (Mesa's libOpenCL implementation) and - Clang/libc++.

In the graphics stack's ports development tree, new Mesa ports + are being worked on. Those ports are required to support GLAMOR + (the GL-based 2D acceleration library used by Radeon HD 7000+ + cards for instance) and OpenCL (using the GPU to perform + non-graphical calculations). We were able to execute some + "Hello World" OpenCL programs and play with OpenCL in darktable, + but there are some compatibility issues between Clover (Mesa's + libOpenCL implementation) and Clang/libc++.

We are preparing an alternate pkg(8) repository with - packages built with WITH_NEW_XORG. The goal is to - ease the usage of the KMS drivers and move forward with the - graphics stack updates. The main pkg(8) repository - will still use the default setting (WITH_NEW_XORG set - on head, but not on the stable - branches).

This will pave the way to WITH_NEW_XORG deprecation - and the removal of the older stack. The current plan is to do - this after 10.0-RELEASE End-of-Life, scheduled on January - 31st, 2015. By that time, the only supported releases will be - 8.4-RELEASE, 9.3-RELEASE and 10.1-RELEASE. &os; 9.3 and 10.1 - will be fully equipped to work with the newer stack. - Unfortunately, &os; 8.x misses the required kernel DRM - infrastructure: supporting X.Org here cripples progress on the - graphics stack and, once WITH_NEW_XORG is gone, we - will not support 8.x as a desktop any more. Therefore, please - upgrade to 9.3 or 10.1 when they are available.

WITH_NEW_XORG

pkg(8)

WITH_NEW_XORG

head

stable

This will pave the way to the deprecation + ofWITH_NEW_XORG and the removal of the older stack. + The current plan is to do this after 10.0-RELEASE End-of-Life, + scheduled on January 31st, 2015. By that time, the only + supported releases will be 8.4-RELEASE, 9.3-RELEASE and + 10.1-RELEASE. &os; 9.3 and 10.1 will be fully equipped to work + with the newer stack. Unfortunately, &os; 8.x misses the + required kernel DRM infrastructure: supporting X.Org here + cripples progress on the graphics stack and, once + WITH_NEW_XORG is gone, we will not support 8.x as a + desktop any more. Therefore, please upgrade to 9.3 or 10.1 when + they are available.

@@ -2198,10 +2196,10 @@ device vt_efifb -

The &os; Port Management Team is to ensure that the &os; - Ports Developer community provides a ports collection that is - functional, stable, up-to-date and full-featured. It is also - to coordinate among the committers and developers who work on +

The role of the &os; Port Management Team is to ensure that the + &os; Ports Developer community provides a ports collection that is + functional, stable, up-to-date and full-featured. It is also to + coordinate among the committers and developers who work on it.

The ports tree slowly approaches the 25,000 ports threshold, @@ -2217,18 +2215,18 @@ device vt_efifb &a.antoine;.

Commencing March 1, the second intake of - portmgr-lurkers started active duty on - portmgr for a four month duration. The next two - candidates are &a.danfe; and &a.culot;.

+ portmgr-lurkers started active duty on portmgr + for a four month duration. The next two candidates are + &a.danfe; and &a.culot;.

This quarter also saw the release of the first quarterly branch, namely 2014Q1. This branch is intended to provide a stable and high-quality ports tree, with patches - related to security fixes as well as packaging and runtime - fixes being backported from head.

+ related to security fixes as well as packaging and runtime fixes + being backported from head.

Ongoing maintenance goes into redports.org, including QAT - runs and ports and security updates.

Ongoing maintenance goes into redports.org, including QAT runs + and ports and security updates.

@@ -2321,7 +2319,7 @@ device vt_efifb

The &os; Postmaster Team is responsible for mail being - correctly delivered to the committers' email address, ensuring + correctly delivered to the committers' email addresses, ensuring that the mailing lists work, and should take measures against possible disruptions of project mail services, such as having troll-, spam- and virus-filters.

@@ -2375,16 +2373,17 @@ device vt_efifb

The first quarter of 2014 was very active for the Core Team. &a.jhb; and &a.theraven; kept coordinating the work required for providing a newer version of X.Org for 9.x and 10.x - systems. Now, after that vt(4), a successor to + systems. Now that vt(4), a successor to syscons(4) that offers a KMS-enabled console, has been merged to both stable/9 and stable/10, an alternative pkg(8) repository is in preparation - for wider testing. In addition to that, &a.jhb; published the + for wider testing of vt(4) and the new X.Org version. + In addition to that, &a.jhb; published the policy on licenses for new files and files with non-standard licenses. Thanks to the efforts of &a.gavin;, &os; has again made it into the Google Summer of Code program, for the tenth - time now. &a.theraven; reported that both libc++ and - libstdc++ can be now built as all the + time. &a.theraven; reported that both libc++ and + libstdc++ can now be built, as all of the standards-compliant implementations of the required numerical functions have been added.

@@ -2407,7 +2406,7 @@ device vt_efifb achieved by increasing the value of __FreeBSD_version on each fix, therefore the corresponding discussion concluded in freezing the ABI note tag for releases in order to keep the - size of the binary patches for freebsd-update(8) low. + size of binary patches for freebsd-update(8) low. A related Errata Notice is about to be published soon.

Only a single commit bit was taken for safekeeping. @@ -2459,7 +2458,7 @@ device vt_efifb Samba permissions. This allows novice users to configure access to shares in various configurations. It allows both control and usability, with no manual being necessary in order - to operate it. This is the ZFSguru-style.

+ to operate it. This is the ZFSguru style.

New system versions have been released, based on &os; 9.2, 10.0, and head. The experimental head @@ -2481,7 +2480,7 @@ device vt_efifb - ZFSguru beta10 will increase compatibility of new added + ZFSguru beta10 will increase the compatibility of newly added Samba functionality with non-Gecko browsers. It will also fix some minor bugs as well as speed up some pages by having a redesigned remote database system called GuruDB. @@ -2500,9 +2499,9 @@ device vt_efifb New website with new forum and new login system. - Developer website with GitLab setup, allowing bugreports, + Developer website with GitLab setup, allowing bug reports, code contributions, wiki, and wall messages. Note that GitLab - has also been provided as ZFSguru service, for those + has also been provided as a ZFSguru service, for those interested in trying GitLab. @@ -2559,7 +2558,7 @@ device vt_efifb

bhyve is a Type-1 hypervisor that runs on the &os; platform. - It currently only runs &os; (9.x or later) and Linux guests, + It currently only runs &os; (9.x or later) and Linux guests; current development efforts aim at widening support for other x86 64-bit operating systems. After a great deal of work by all involved, bhyve was shipped as part of &os; 10.0-RELEASE. @@ -2577,8 +2576,8 @@ device vt_efifb

Graceful shutdown via ACPI on SIGTERM

Fix issue with virtio-blk devices on Linux guests with - more than 4GB of ram

Fix an issue with virtio-blk devices on Linux guests with + more than 4GB of RAM

Increase the block-layer backend maximum requests to match AHCI command queue depth