svn commit: r46191 - head/en_US.ISO8859-1/htdocs/news/status
David Chisnall
theraven at FreeBSD.org
Mon Jan 12 19:00:52 UTC 2015
Author: theraven (src,ports committer)
Date: Mon Jan 12 19:00:51 2015
New Revision: 46191
URL: https://svnweb.freebsd.org/changeset/doc/46191
Log:
Proof read and add a first pass at an intro.
Modified:
head/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml
Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml Mon Jan 12 03:17:54 2015 (r46190)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2014-10-2014-12.xml Mon Jan 12 19:00:51 2015 (r46191)
@@ -26,8 +26,18 @@
December 2014. This is the last of four reports planned for
2014.</p>
- <p>The fourth quarter of 2014... was a very busy and productive
- time</p>
+ <p>The fourth quarter of 2014 included a number of significant improvements to the &os;
+ system, in particular in compatibility with other systems. This included
+ significant improvements to the Linux compatibility layer, used to
+ run Linux binaries on &os;, and the port of WINE, used to run Windows
+ applications. Hypervisor support improved, with &os; gaining the ability
+ to run as domain 0 on Xen's new high-performance PVH mode, bhyve gaining
+ AMD support, and new tools for creating &os; VM images arriving.</p>
+
+ <p>This quarter was also an active time for the toolchain, with numerous
+ improvements to the compiler, debugger, and other components, including
+ initial support for C++14, which should be complete by
+ &os; 10.2.</p>
<p>Thanks to all the reporters for the excellent work!</p>
@@ -97,7 +107,7 @@
<p>With funding from the &os; Foundation, the &os; forums
were migrated to XenForo software. The new software is far more
capable and easy to use. While the entire forum team
- contributed, &a.danger; did a particularly excellent job
+ contributed, &a.danger; did an excellent job
importing existing users and messages and bringing back the
often-requested "Thanks" feature. The upgrade was completed in
time to be ready for the influx of new users from the release of
@@ -151,8 +161,9 @@
<body>
<p>There were several improvements made to the FreeBSD process
management last quarter.</p>
+ <!-- This needs some markup from someone with more docbook-fu than me -->
- <p>Reaper. The facility to allow a process to reliably track the
+ <p>The Reaper facility, to allow a process to reliably track the
running and exiting state of the whole subtree of the processes,
was added. It is intended to improve tools like timeout(1) or
poudriere, by making it impossible for the runaway granchild to
@@ -161,36 +172,36 @@
references to the Solaris contracts. Committed to HEAD in
r275800.</p>
- <p>Total stop. Right now, the FreeBSD suspension code does not
- ensures that the system, both from software and from hardware
- view, is in the steady and consistent state. One aspect is the
- usermode process activity which is not stopped, continuing to
+ <p>The FreeBSD suspension code does not
+ ensure that the system, both software and hardware,
+ is in the steady and consistent state. One aspect is
+ usermode process activity, which is not yet stopped, continuing to
making requests to the hardware. It is not realistic to expect
drivers to be able to correctly handle the calls after
SUSPEND_CHILD.</p>
- <p>Together with Peter Holm, we developed a facility to stop
- usermode threads at the safe points, where they are known to not
+ <p>We developed a facility to stop
+ usermode threads at safe points, where they are known to not
own and to not wait for kernel resources, in particular, not
waiting for device requests finishing. It is based on the
existing single-threading code, but extending it to allow external
- thread to put some process into stopped state. Also, a facility
+ thread to put some processes into stopped state. Also, a facility
to sync filesystems before suspend was added, to ensure that
consistent metadata and as much as possilbe of the cached user
data are on stable storage, to minimize damage of failed
resume.</p>
- <p>The code stressed some parts of the system and lead to
- discovery of the unusual numbers of bugs in the different parts of
- the system, including process management, buffer cache and syscall
+ <p>The code stressed some parts of the system and has lead to
+ discovery of a numbers of bugs in the different areas,
+ including process management, buffer cache and syscall
handlers. The bugs were fixed, fixes and the features commmitted
by a series culminating in r275745.</p>
- <p>Process spinlock changes. During the work described above, it
+ <p>During the work described above, it
was noted that process spinlock duties are significantly
overloaded (the same is true for the process lock). The spinlock
- was split into per-feature lock, see r275121. Also, as result, it
- was possible to eliminate recursion on it, r275372.</p>
+ was split into per-feature locks, in r275121. Also, as result, it
+ was possible to eliminate recursion on it, in r275372.</p>
</body>
<sponsor>The FreeBSD Foundation</sponsor>
@@ -298,8 +309,8 @@
improving the <tt>pkg(8)</tt> experience on small/embedded
machines (reduce memory usage, speed up operations).</p>
- <p><tt>pkg(8)</tt> is not only the &os; Package Manager, but the
- Package Manager for DragonflyBSD. Additionally support has been
+ <p><tt>pkg(8)</tt> is not only the &os; Package Manager, but also the
+ Package Manager for DragonflyBSD. Support has been
added to build <tt>pkg(8)</tt> on OS X and Linux. This work
will allow other Operating Systems the option of adopting
<tt>pkg(8)</tt> to manage their packages and bring new
@@ -372,11 +383,11 @@
reported by <tt>mdoc(7)</tt> in the FreeBSD manual pages. This
greatly improves the quality of our manual pages.</p>
- <p>Most manual pages with remaining issues are from contrib/ for
+ <p>Most manual pages with remaining issues are from contrib/, for
which changes should be reported and fixed upstream.</p>
<p>The "manlint" target has also been switch to use <tt>mandoc
- -Tlint</tt> which results in the target being way more useful
+ -Tlint</tt>, which results in the target being more useful
when working on manual pages.</p>
<p>Some <tt>groff(1)</tt> vs <tt>mandoc(1)</tt> formatting
@@ -390,12 +401,12 @@
<tt>mandoc(1)</tt>.</p>
</task>
<task>
- <p>Figure out a way to detect non <tt>mandoc(1)</tt> friendly
+ <p>Figure out a way to detect non <tt>mandoc(1)</tt> unfriendly
manpages from ports and create catpages with <tt>groff(1)</tt>
for them.</p>
</task>
<task>
- <p>Remove <tt>groff(1)</tt> from base.</p>
+ <p>Remove <tt>groff(1)</tt> from the base system.</p>
</task>
</help>
</project>
@@ -436,13 +447,13 @@
to build world and kernel with non default toolchain. It can be
helpful to:
<ul>
- <li>Prepare a migration to a newer version of the components like compilers, binutils, and elftoolchain.</li>
+ <li>Prepare a migration to a newer version of toolchain components.</li>
<li>Port &os; to newer architecture</li>
- <li>Upgrade from a &os; that ships with GCC 4.2 to a version that ship with clang 3.5+ (which need a more modern toolchain than GCC 4.2 to bootstrap.</li>
+ <li>Upgrade from a &os; that ships with GCC 4.2 to a version that ship with clang 3.5+ (which need a more modern toolchain than GCC 4.2 to bootstrap).</li>
</ul>
</p>
- <p>The initial support for external toolchain only supported
+ <p>The initial external toolchain work only supported
clang. It has been extended to support recent GCC (4.9.1 has
been tested) and recent binutils (2.24 and 2.25).</p>
@@ -454,8 +465,8 @@
the kernel to make sure it is possible to build the kernel with
recent GCC (first 4.6 and then 4.9.1)</p>
- <p>The build system has been changed to build libc++ as a C++
- stack when a recent enough GCC (4.6+) is used to build world.
+ <p>The build system has been changed to build libc++ as the C++
+ standard library implementation when a recent enough GCC (4.6+) is used to build world.
</p>
<p>To simplify using an external toolchain, the following
@@ -549,14 +560,14 @@
<p>This quarter was exciting time for the GNOME Team. We imported
GNOME 3.14.0 and CINNAMON 2.2.16 into the ports tree. At the same
time we removed the old GNOME 2.32 desktop. And two weeks later
- we updated GNOME to 3.14.2 and CINNAMON to 2.4.2 which was collected
+ we updated GNOME to 3.14.2 and CINNAMON to 2.4.2, which was collected
while the preparation for the initial GNOME 3.14.0 import was
underway.</p>
- <p>We moved our development repo to GitHub. The link is in the links
- section. The repo is structured as follows: the <tt>master</tt> branch
+ <p>We moved our development repo to GitHub.
+ The repo is structured as follows: the <tt>master</tt> branch
is vanilla &os; Ports, and we have <tt>theme branches</tt> for topics,
- like the porting of MATE 1.9 (mate-1.10 branch) and GNOME 3.15
+ such as the porting of MATE 1.9 (mate-1.10 branch) and GNOME 3.15
(gnome-3.16 branch). The GNOME 3.14 branch (gnome-3.14) is not
used/updated anymore because the content has been committed to
ports, but is kept around for the history.</p>
@@ -848,10 +859,10 @@
the Jenkins 1.586 release. This fixed problems with PAM
authentication support in Jenkins on FreeBSD [JENKINS-21507].</li>
- <li>&a.rodrigc; gave a presentation Kyua and Jenkins Testing
- Framework for BSD at the Developer and Vendor summit on
+ <li>&a.rodrigc; gave a presentation "Kyua and Jenkins Testing
+ Framework" for BSD at the Developer and Vendor summit on
November 3, 2014 in San Jose, California. In the presentation,
- &a.rodrigc;'s described how for every commit to the FreeBSD source
+ &a.rodrigc;'s described how, for every commit to the FreeBSD source
tree, nearly 3000 tests are run using kyua inside a bhyve virtual
machine. The kyua test results are exported to JUnit XML format,
which is then used by Jenkins to generate web-based test reports with
@@ -1077,9 +1088,9 @@
<p>xserver was upgraded from 1.12 to 1.14. This is the last version
of xserver supporting Mesa 9.1. Changes are described in an article
- on the blog. The most noticeable one is probably the switch from
+ on the blog. The most noticeable one is the switch from
the input device detection back-end based on HAL to the one based on
- devd. hald(8) is still required by many desktop environments, but
+ devd(8). hald(8) is still required by many desktop environments, but
the X.Org server itself is free from it.</p>
<p>xserver was the last port supporting the <tt>WITH_NEW_XORG</tt>
@@ -1089,14 +1100,14 @@
At the same time, the new-xorg alternate pkg repository was
deprecated.</p>
- <p>After discussion, two patent-encumbered options were enabled by
- default:</p>
+ <p>After discussion, two options were enabled by default:</p>
<ul>
<li><tt>TEXTURE_FLOAT</tt> in graphics/dri, which allows Mesa to
advertise the support for OpenGL 3.0+;</li>
<li><tt>LCD_FILTERING</tt> in print/freetype2, which enables the
subpixel rendering engine, improving font anti-aliasing.</li>
</ul>
+
<p>These two packages now provide a better user experience
out-of-the-box. Users who are uncomfortable with the options may
unset them and rebuild the ports. There is no need to rebuild
@@ -1235,7 +1246,7 @@
<body>
<p>During this quarter almost all pending Xen changes have been
- committed, enabling the usage of FreeBSD as Dom0 under the new
+ committed, enabling FreeBSD to be used as Dom0 under the new
PVH mode. The set of features supported by FreeBSD is still limited,
but it should allow for basic usage of FreeBSD as Dom0. Support for
booting Xen from the FreeBSD boot loader will be committed very soon
@@ -1309,7 +1320,7 @@
<body>
<p>Just before the end of the year, we have updated clang,
- llvm and lldb in base to 3.5.0 release. These all contain
+ llvm and lldb in the base system to 3.5.0 release. These all contain
numerous improvements; please see the linked release notes for
more detailed information.</p>
@@ -1366,7 +1377,7 @@
of &os;, announcing code freezes and maintaining the
respective branches, among other things.</p>
- <p>The &os; 10.1-RELEASE cycle completed November 14th,
+ <p>The &os; 10.1-RELEASE cycle completed on November 14th,
marking the second official release point from the
<tt>stable/10</tt> branch, just short of three weeks later
than the original schedule anticipated.</p>
@@ -1412,8 +1423,8 @@
Some highlights of the work in this area include the following:</p>
<ul>
- <li>&a.alfred; requested the creation of a new mailing list
- freebsd-git at FreeBSD.org. This list is for discussion of
+ <li>At &a.alfred;'s request, a new mailing list
+ freebsd-git at FreeBSD.org was created for discussion of
git use in the FreeBSD project.</li>
<li>&a.alfred; submitted a patch to git. This patch allows a
@@ -1477,7 +1488,7 @@
</links>
<body>
- <p>The ELF Tool Chain project provides BSD licensed
+ <p>The ELF Tool Chain project provides BSD-licensed
implementations of compilation tools and libraries for building
and analyzing ELF objects. It started as part of &os; but has
moved to a standalone project to encourage wider participation
@@ -1510,8 +1521,8 @@
missing functionality in ELF note parsing is added. ELF Tool
Chain's elfcopy provides equivalent functionality to Binutils
objcopy, and accepts the same command-line arguments. For it to be
- a viable replacement for all uses of objcopy in the base system it
- will need to gain support for writing portable exectuable (PE)
+ a viable replacement for all uses of objcopy in the base system, it
+ must gain support for writing portable exectuable (PE)
format binaries, which are used in by UEFI boot code.</p>
<p>The ELF Tool Chain project does not currently provide
@@ -1808,7 +1819,7 @@
<body>
<p>The main goal of the lemul project is the execution of
- multithreaded Linux applications, which requires the glibc library
+ multithreaded Linux applications that requires the glibc library
version 2.20 or later to be available on &os;. Glibc 2.20
requires a Linux kernel (or emulation thereof) of version 2.6.32
or later. The main obstacle preventing this is that the current
@@ -2022,13 +2033,15 @@
</links>
<body>
- <p>The ports framework's Linux emulation stack was upgraded to
+ <p>The ports collection's Linux emulation stack was upgraded to
include CentOS 6.6 on November 11. After smoothing out
several bugs that had been introduced, we have been able to bump
the default version of the Linux userland from Fedora 10 to
CentOS 6.6 on December 9. Providing a more
- modern Linux userland and supporting libraries allows a great
- number of Linux applications to be run on &os;. The goal
+ modern Linux userland and supporting libraries allows a large
+ number of Linux applications to be run on &os;.</p>
+
+ <p>The goal
behind providing an updated Fedora-based userland is to support
more desktop-oriented applications, which require newer libraries
than are provided by CentOS 6. Providing 64-bit versions of
@@ -2293,7 +2306,7 @@
to work with machine-readable output instead of human-readable
output.</p>
- <p>Juniper Networks has created a library called libxo, that
+ <p>Juniper Networks has created a library called libxo, which
makes it easy for utilities to emit output in various
formats. By default the text output is emitted, but with the
introduction of the <tt>—libxo</tt> option this can be changed to
More information about the svn-doc-all
mailing list