svn commit: r43637 - head/en_US.ISO8859-1/htdocs/news/status
Gabor Pali
pgj at FreeBSD.org
Fri Jan 24 00:55:33 UTC 2014
Author: pgj
Date: Fri Jan 24 00:55:33 2014
New Revision: 43637
URL: http://svnweb.freebsd.org/changeset/doc/43637
Log:
- Language fixes to the 2013Q4 report [1]
- Use the <sponsor> tag for the Intel GPU update entry
Submitted by: bjk [1]
Modified:
head/en_US.ISO8859-1/htdocs/news/status/report-2013-10-2013-12.xml
Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2013-10-2013-12.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2013-10-2013-12.xml Thu Jan 23 20:32:49 2014 (r43636)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2013-10-2013-12.xml Fri Jan 24 00:55:33 2014 (r43637)
@@ -133,11 +133,11 @@
continuously run are obvious: regressions can be caught sooner
rather than later and the Release Engineering Team can better
assess the quality of the tree before deciding to cut a release.
- Additionally, and because we choose to install the tests, we
- also allow any end user to perform sanity checks on new
- installations of the system on his or her particular hardware
- configuration — a very attractive thing to do when
- deploying production servers.</p>
+ Additionally, because we choose to install the tests, we allow
+ any end user to perform sanity checks on new installations of
+ the system on their particular hardware configuration — a
+ very attractive thing to do when deploying production
+ servers.</p>
<p>During the last few months, we have added the necessary pieces to
the build system to support building and installing test programs of
@@ -777,9 +777,9 @@
<p>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 analytics
- engine, which can be integrated with cloud orchestration systems
- like OpenStack or CloudStack.</p>
+ comprising a network controller, a virtual router, and an
+ analytics engine, which can be integrated with cloud
+ orchestration systems like OpenStack or CloudStack.</p>
<p>The goal of this work is to enable &os; as a fully supported
compute host for OpenStack, using OpenContrail virtualized
@@ -793,7 +793,7 @@
<li>OpenContrail vRouter (forwarding-plane kernel module) port
to &os;.</li>
- <li>Integration, performance optimizations.</li>
+ <li>Integration and performance optimizations.</li>
</ul>
<p>The current state of development features a working demo of
@@ -807,12 +807,12 @@
<li>The <tt>nova-network</tt> approach (based on local host
bridging) is becoming an obsolete technology in OpenStack and
- was used here only for a demonstration and proof-of-concept
+ was used here only for demonstration and proof-of-concept
purposes, without exploring all the possible features.</li>
<li>The main objective is to move to OpenContrail-based
- networking, therefore become compliant with the modern OpenStack
- networking API ("neutron").</li>
+ networking, therefore becoming compliant with the modern
+ OpenStack networking API ("neutron").</li>
</ul>
</body>
@@ -872,7 +872,7 @@
<task>Implement &os; ARM support.</task>
<task>Add support for kernel debugging (live local and remote
debugging, and core files).</task>
- <task>Fix remaining test suite failures.</task>
+ <task>Fix the remaining test suite failures.</task>
<task>Enable by default on the <tt>amd64</tt> architecture.</task>
</help>
</project>
@@ -923,8 +923,8 @@
<help>
<task>Resolve a 32- vs 64-bit <tt>libstand(3)</tt> build issue.</task>
<task>Merge kernel parsing of EFI memory map metadata.</task>
- <task>Integrate EFI framebuffer with <tt>vt(9)</tt> (also known as
- Newcons).</task>
+ <task>Integrate the EFI framebuffer with <tt>vt(9)</tt> (also
+ known as Newcons).</task>
<task>Connect <tt>efiloader</tt> to the build.</task>
<task>Document manual installation for dual-boot configurations.</task>
<task>Integrate UEFI configuration with the &os; installer.</task>
@@ -958,12 +958,13 @@
MATE is a desktop environment forked from the now-unmaintained
code base of GNOME 2, therefore it is basically a
replacement for GNOME 2. It recommended for users wanting
- to keep GNOME 2 as their desktop to switch as GNOME 2
- will be replaced by GNOME 3 in the near future. This
- switch will be announced in advance, so people will have time to
- move to MATE if they have not already. The complete MATE-based
- desktop environment can be installed via the <tt>x11/mate</tt>
- port, or, for a minimal install, <tt>x11/mate-base</tt>.</p>
+ to keep GNOME 2 as their desktop to switch since
+ GNOME 2 will be replaced by GNOME 3 in the near
+ future. This switch will be announced in advance, so people
+ will have time to move to MATE if they have not already. The
+ complete MATE-based desktop environment can be installed via the
+ <tt>x11/mate</tt> port, or, for a minimal install,
+ <tt>x11/mate-base</tt>.</p>
<p>Our home page is quite out of date. An update for it for
GNOME 3.6 is underway. Part of this update is rewriting
@@ -971,19 +972,20 @@
Porter's Handbook.</p>
<p>Another major task required for getting a bleeding-edge GNOME
- build on &os; mostly out-of-the box is moving to JHbuild with
+ to build on &os; mostly out-of-the box is moving to JHbuild with
some custom rules. This is done to find and fix compile issues
on other BSDs more quickly.</p>
</body>
<help>
<task>GNOME 2 ports still need to be sorted out to evaluate
- which GNOME 2 components will gone or be replaced with
+ which GNOME 2 components will be gone or be replaced with
their newer GNOME 3 versions. This task is current halted
until we can get the documentation into a shape good enough to
- gather the issues and document the migration, including how not
- to do that when the upgrade is not preferred. (This does not
- mean we do not want to know about these issues, though).</task>
+ gather the issues and document the migration, including how to
+ to avoid the migration if the upgrade is not preferred. (This
+ does not mean we do not want to know about issues with
+ upgrading, though).</task>
<task>Help the X11 Team with Cairo 1.12, since the next
version of GNOME 3 (3.12) will need an up-to-date version
@@ -1005,15 +1007,17 @@
</contact>
<body>
- <p>This &os; Foundation-sponsored project will update the Intel
- graphics chipset driver, <tt>i915kms</tt>, to a recent snapshot
- of the Linux upstream code. The update will provide at least
- 1.5 years of bugfixes from the Intel team, and introduce support
- for the newest hardware — in particular Haswell and
- ValleyView. The IvyBridge code will also be updated. Addition
- of several features, which are required for the update of X.Org
- and Mesa, is also planned.</p>
+ <p>This project will update the Intel graphics chipset driver,
+ <tt>i915kms</tt>, to a recent snapshot of the Linux upstream
+ code. The update will provide at least 1.5 years of bugfixes
+ from the Intel team, and introduce support for the newest
+ hardware — in particular Haswell and ValleyView. The
+ IvyBridge code will also be updated. The addition of several
+ features, which are required in order to update X.Org and Mesa,
+ is also planned.</p>
</body>
+
+ <sponsor>The &os; Foundation</sponsor>
</project>
<project cat='kern'>
@@ -1108,10 +1112,10 @@
network configuration dialogues to make the identification of
wireless interfaces easier.</p>
- <p>A number of additional features are also planned. Allow the
- user to create additional datasets and adjust the properties on
- all datasets in an interactive menu. Also integrate BSDConfig
- to allow users to install packages and various other
+ <p>A number of additional features are also planned. The
+ user should be able to create additional datasets and adjust the properties on
+ all datasets in an interactive menu. There should also be integration with BSDConfig
+ to allow users to install packages and the various other
functionality that was previously provided by
<tt>sysinstall</tt>.</p>
</body>
@@ -1148,20 +1152,20 @@
<body>
<p>At the November 2013 &os; Vendor Summit, some of the work was
- presented that Craig Rodrigues have been doing with Continuous
+ presented that Craig Rodrigues has been doing with Continuous
Integration and Testing at iXsystems. Craig's presentation
described how iXsystems is using modern best practices for
- building and testing FreeNAS code. Jenkins is a framework for
- doing continuous builds and integration, and is used by hundreds
- of companies. BHyve (BSD Hypvervisor) is the new virtual
- machine system which will be part of &os; 10. Webdriver is
- a Python toolkit for testing web applications. By combining
- these technologies, iXsystems is developing a modern and
- sophisticated workflow for testing and improving the quality of
- FreeNAS.</p>
+ building and testing the FreeNAS code. Jenkins is a framework
+ for doing continuous builds and integration that is used by
+ hundreds of companies. BHyve (BSD Hypvervisor) is the new
+ virtual machine system which will be part of &os; 10.
+ Webdriver is a Python toolkit for testing web applications. By
+ combining these technologies, iXsystems is developing a modern
+ and sophisticated workflow for testing and improving the quality
+ of FreeNAS.</p>
<p>Ed Maste from The &os; Foundation was interested in this work,
- and based on this interest, now it is being ported to &os;.
+ and based on this interest, it is now being ported to &os;.
Currently, a machine in the &os; cluster has been allocated for
this purpose, where a <tt>bhyve(4)</tt>-based virtual machine
was set up and Jenkins was installed. The remainder is still in
@@ -1218,14 +1222,15 @@
<tt>freebsd-x11</tt> mailing-list (see the links above) to
gather information about the behavior on other configurations
(new Intel driver and non-Intel drivers). As of this writing,
- received reports talk about improvements or, at least, no change
- noticed.</p>
+ the reports received talk about improvements or, at least, no
+ change noticed.</p>
<p>To better manage changes such as the <tt>WITH_NEW_XORG</tt> and
- Cairo 1.12 mentioned above, we asked on <tt>freebsd-x11</tt>
- mailing-list if people are using &os; 8.x on their desktop
- computers and why they do not upgrade to &os; 9.x or 10.x.
- So far, we received very few answers to this.</p>
+ Cairo 1.12 changes mentioned above, we asked on the
+ <tt>freebsd-x11</tt> mailing-list if people are using
+ &os; 8.x on their desktop computers and why they do not
+ upgrade to &os; 9.x or 10.x. So far, we received very few
+ answers to this.</p>
<p>The Radeon KMS driver in &os; 10.x is now considered
stable, especially that integrated GPUs are now properly
@@ -1272,7 +1277,7 @@
<p>Research and prototyping has begun on a new project to
implement <tt>autofs(4)</tt> — an automounter filesystem
— and its userland counterpart, <tt>automountd(8)</tt>.
- The idea is to provide very similar user experience to the
+ The idea is to provide a very similar user experience to the
automounters available on Linux, MacOS X, and Solaris, including
using the same map format. The automounter will also integrate
with directory services, such as LDAP.</p>
@@ -1366,9 +1371,10 @@ device vt_vga</pre>
<ul>
<li>Switching to <tt>vty0</tt> from X.Org on Fatal events will not work.</li>
- <li>Certain hardware (eg. Lenovo X220) get black screen when i915kms is preloaded.</li>
+ <li>Certain hardware (eg. Lenovo X220) get a black screen when
+ i915kms is preloaded.</li>
<li>Scrolling can be slow;</li>
- <li>Screen borders is not cleared when changing fonts.</li>
+ <li>Screen borders are not cleared when changing fonts.</li>
<li><tt>vt(9)</tt> locks up with the <tt>gallant12x22</tt> font in VirtualBox.</li>
</ul>
</body>
@@ -1503,9 +1509,9 @@ device vt_vga</pre>
<p>Ongoing effort went into testing larger changes, as many as 8 a
week, including sweeping changes to the tree, moderization of
the infrastructure, and basic quality assurance (QA) runs. Many
- iterations of <tt>10.0-RELEASE</tt> tests were run to ensure the
- maximum amount of packages would be available for the
- release.</p>
+ iterations of tests against <tt>10.0-RELEASE</tt> were run to
+ ensure that the maximum number of packages would be available
+ for the release.</p>
<p>We now have <tt>pkg(8)</tt> packages for the releases 8.3, 8.4,
9.1, 9.2, 10.0 and -CURRENT on <tt>pkg.FreeBSD.org</tt>. During
@@ -1523,8 +1529,8 @@ device vt_vga</pre>
</body>
<help>
- <task>As previously noted, many PRs continue to languish, we would
- like to see a committers dedicate themselves to closing as many
+ <task>As previously noted, many PRs continue to languish; we would
+ like to see some committers dedicate themselves to closing as many
as possible!</task>
</help>
</project>
@@ -1542,8 +1548,8 @@ device vt_vga</pre>
<body>
<p>The &os; Cluster Administration Team consists of the people
- responsible for administrating the machines that the project
- relies on for its distributed work and communication to be
+ responsible for administering the machines that the project
+ relies on for its distributed work and communications to be
synchronised. In the last quarter of 2013, they continued
general maintenance of the &os; cluster across all sites.</p>
@@ -1583,13 +1589,13 @@ device vt_vga</pre>
</links>
<body>
- <p>Basic support for Freescale Vybrid Family VF6xx heterogeneous
- ARM Cortex-A5/M4 System-on-Chip (SoC) was added to &os;
- <tt>head</tt>. The Vybrid VF6xx family is an implementation of
- the new modern Cortex-A5-based low-power ARM SoC boards. Vybrid
- devices are ideal for applications including simple HMI in
- appliances and industrial machines, secure control of
- infrastructure and manufacturing equipment, energy conversion
+ <p>Basic support for the Freescale Vybrid Family VF6xx
+ heterogeneous ARM Cortex-A5/M4 System-on-Chip (SoC) was added to
+ &os; <tt>head</tt>. The Vybrid VF6xx family is an
+ implementation of the new modern Cortex-A5-based low-power ARM
+ SoC boards. Vybrid devices are ideal for applications including
+ simple HMI in appliances and industrial machines, secure control
+ of infrastructure and manufacturing equipment, energy conversion
applications such as motor drives and power inverters,
ruggedized wired and wireless connectivity, and control of
mobile battery-operated systems such as robots and industrial
@@ -1641,10 +1647,10 @@ device vt_vga</pre>
the last six months:</p>
<ul>
- <li>New hardware support, 2xxx, 6xxx, 1xx series hardware.</li>
+ <li>New hardware support: 2xxx, 6xxx, 1xx series hardware.</li>
- <li>Many bugs fixed, including scanning, association, EAPOL related
- fixes.</li>
+ <li>Many bugs were fixed, including scanning, association, EAPOL
+ related fixes.</li>
<li><tt>iwn(4)</tt> now natively works with 802.11n rates from the
net80211 rate control code, rather than mapping non-11n rates to 11n
@@ -1656,7 +1662,7 @@ device vt_vga</pre>
<task>There are still some scan hangs, due to how net80211 scans a
single channel at a time. This needs to be resolved.</task>
- <task>The transmit, receive, scan and calibration code need to be
+ <task>The transmit, receive, scan and calibration code needs to be
refactored out of <tt>if_iwn.c</tt> and into separate source
files.</task>
@@ -1773,7 +1779,7 @@ device vt_vga</pre>
<p>As a result, according to PortScout, our team has 464 ports
(down from 473), of which 88.15% are up-to-date (down from
- 98.73%). iXsystems Inc. continues to provided a machine for
+ 98.73%). iXsystems Inc. continues to provide a machine for
the team to build packages and to test updates. iXsystems Inc.
has been providing the KDE/&os; Team with support for quite a
long time and we are very grateful for that.</p>
@@ -1825,7 +1831,7 @@ device vt_vga</pre>
Reaper</q> service which helps to enforce the aforementioned
policy.</p>
- <p>Along with the works of John Baldwin and Hiroki Sato, many
+ <p>With the work of John Baldwin, Hiroki Sato, and others, many
licenses in the base system source code have been revisited and
cleaned up. Furthermore, the Core Team is hoping that the
situation can be improved by introducing periodic automated
@@ -1863,21 +1869,22 @@ device vt_vga</pre>
<p>The GCC compiler in the &os; base system is on its way to
deprecation and is only used by some Tier-2 platforms at this
time. While Clang is much better in many aspects, we still
- cannot use in base all the new features it brings until we can
- drop GCC completely. As a stop-gap solution several bug fixes
- and features from Apple GCC and other sources have been ported
- to our version of GCC 4.2.1 to make it more compatible with
- Clang. &os;'s GCC has added more warnings and some enhancements
- like <tt>-Wmost</tt> and <tt>-Wnewline-eof</tt>. An
- implementation for Apple's blocks extension is now available too
- and it will be very useful to enhance &os;'s support for Apple's
- Grand Central Dispatch (GCD).</p>
+ cannot use in the base system all the new features that it
+ brings until we can drop GCC completely. As a stop-gap
+ solution, several bug fixes and features from Apple GCC and
+ other sources have been ported to our version of GCC 4.2.1
+ to make it more compatible with Clang. &os;'s GCC has added
+ more warnings and some enhancements like <tt>-Wmost</tt> and
+ <tt>-Wnewline-eof</tt>. An implementation for Apple's blocks
+ extension is now available, too, and it will be very useful to
+ enhance &os;'s support for Apple's Grand Central Dispatch
+ (GCD).</p>
</body>
<help>
- <task>Merge from <tt>head</tt> to <tt>stable/9</tt> is being
- considered but it disables nested functions by default so the
- impact on ports has to be evaluated.</task>
+ <task>A merge from <tt>head</tt> to <tt>stable/9</tt> is being
+ considered but it disables nested functions by default, so the
+ impact on the Ports Collection needs to be evaluated.</task>
<task>No further development of GCC 4.2 in the base system is
planned.</task>
@@ -1915,8 +1922,8 @@ device vt_vga</pre>
processing donations and will post the final numbers by
mid-January. We are extremely grateful to all the individuals
and organizations that supported us and the Project by making a
- donation in 2013. We already started our fundraising efforts
- for 2014.</p>
+ donation in 2013. We have already started our fundraising
+ efforts for 2014.</p>
<p>Some of the highlights from this past quarter include:</p>
@@ -1945,7 +1952,7 @@ device vt_vga</pre>
<li>Sponsored and attended the OpenZFS developer summit.</li>
<li>Represented the foundation at the following conferences: All
- Things Open in Raleigh, NC and LISA in DC.</li>
+ Things Open in Raleigh, NC and LISA in Washington, DC.</li>
<li>Sponsored the &os; 20th Birthday Party, held in San
Francisco.</li>
@@ -2006,12 +2013,12 @@ device vt_vga</pre>
<body>
<p>An Input/Output Memory Management Unit (IOMMU) is a Memory
Management Unit (MMU) that connects a Direct Memory
- Access-capable (DMA-capable) I/O bus to the main memory,
- therefore I/O virtualization is performed by the chipset. An
- example IOMMU is the graphics address remapping table (GART)
- used by AGP and PCI Express graphics cards. Intel has published
- a specification for IOMMU technology as Virtualization
- Technology for Directed I/O, abbreviated VT-d.</p>
+ Access-capable (DMA-capable) I/O bus to main memory; therefore,
+ I/O virtualization is performed by the chipset. An example
+ IOMMU is the graphics address remapping table (GART) used by AGP
+ and PCI Express graphics cards. Intel has published a
+ specification for IOMMU technology as Virtualization Technology
+ for Directed I/O, abbreviated VT-d.</p>
<p>A VT-d driver was committed to <tt>head</tt> and
<tt>stable/10</tt>, so <tt>busdma(9)</tt> is now able to utilize
@@ -2019,7 +2026,7 @@ device vt_vga</pre>
via the <tt>hw.dmar.enable</tt> <tt>loader(8)</tt> tunable
— see the links for more information. The immediate plans
include increasing the support for this kind of hardware by
- testing and providing the workarounds for specific issues, and
+ testing and providing workarounds for specific issues, and
by adding features of the next generation of Intel IOMMU.
Hopefully, the existing and new consumers of VT-d will start to
use the driver soon.</p>
@@ -2070,8 +2077,8 @@ device vt_vga</pre>
Patches have been posted, and after a couple of rounds of review
the series looks almost ready for merging into <tt>head</tt>.
Also, very initial patches for &os; PVH Dom0 support has been
- posted. So far the posted series only focus on getting &os;
- booting as Dom0 and being able to interact with the
+ posted. So far the posted series only focuses on getting &os;
+ booting as a Dom0 and being able to interact with the
hardware.</p>
</body>
@@ -2079,7 +2086,7 @@ device vt_vga</pre>
<sponsor>Spectra Logic Corporation</sponsor>
<help>
- <task>Finish review and commit PVH DomU support.</task>
+ <task>Finish reviewing and commit the PVH DomU support.</task>
<task>Work on PVH Dom0 support.</task>
</help>
</project>
More information about the svn-doc-all
mailing list