svn commit: r47626 - head/en_US.ISO8859-1/htdocs/news/status
Warren Block
wblock at FreeBSD.org
Mon Oct 19 01:35:10 UTC 2015
Author: wblock
Date: Mon Oct 19 01:35:08 2015
New Revision: 47626
URL: https://svnweb.freebsd.org/changeset/doc/47626
Log:
Editing pass.
Modified:
head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml
Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml Sun Oct 18 23:13:53 2015 (r47625)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml Mon Oct 19 01:35:08 2015 (r47626)
@@ -84,7 +84,7 @@
</category>
<project cat='kern'>
- <title>ioat(4) driver import</title>
+ <title><tt>ioat(4)</tt> Driver Import</title>
<contact>
<person>
@@ -108,11 +108,11 @@
<url href="https://en.wikipedia.org/wiki/I/O_Acceleration_Technology">Wikipedia
article on IOAT</url>
<url href="https://svnweb.FreeBSD.org/base?view=revision&revision=r287117">Commit
- importing ioat(4)</url>
+ importing <tt>ioat(4)</tt></url>
</links>
<body>
- <p>A new driver, ioat(4), was added to the tree. ioat(4)
+ <p>A new driver, <tt>ioat(4)</tt>, was added to the tree. <tt>ioat(4)</tt>
supports Intel's I/O Acceleration Technology devices which are found
on some Intel server systems.</p>
@@ -122,7 +122,7 @@
applications must be adapted to take advantage of the hardware.</p>
<p>Some I/OAT models support more advanced copying modes, like
- XOR; these modes are not yet supported in the ioat(4) driver.</p>
+ XOR; these modes are not yet supported in the <tt>ioat(4)</tt> driver.</p>
</body>
<sponsor>
@@ -224,7 +224,7 @@
been added to the system that replicate the functionality of the
TCPDEBUG kernel option. No new kernel options need to be added
— they are standard with any kernel that has DTrace, which
- is included in the default GENERIC kernels in 10.x and HEAD.
+ is included in the default GENERIC kernels in 10.X and HEAD.
</p>
</body>
@@ -257,27 +257,27 @@
<body>
<p>The Acer C720 Chromebook is an affordable (under $200) and
- powerful little laptop, that provides a battery life of up to six
- hours running FreeBSD. It is a great machine for travelling and
+ powerful little laptop that provides a battery life of up to six
+ hours running &os;. It is a great machine for travelling and
coding in general. The machine is fully functional, meaning that
- all essential devices work: Keyboard, trackpad, light sensor,
+ all essential devices work: keyboard, trackpad, light sensor,
backlight control, display in VESA mode (fast), external Display
on HDMI (only VESA mirror mode), sound, USB ports, SD card slot,
- camera and Atheros Wireless.</p>
+ camera, and Atheros wireless.</p>
<p>This quarter, this project extended previous work on the
- boot process and keyboard driver as well as the smbus(4) driver.
- It added three new drivers: ig4(4), cyapa(4) and isl(4).</p>
+ boot process and keyboard driver as well as the <tt>smbus(4)</tt> driver.
+ It added three new drivers: <tt>ig4(4)</tt>, <tt>cyapa(4)</tt>, and <tt>isl(4)</tt>.</p>
- <p>Much of the development was originally done in late 2014;
- since then, the patches have been massively improved and merged
+ <p>Much of the development was originally done in late 2014.
+ Since then, the patches have been massively improved and merged
into CURRENT, so that all relevant devices work without manual
patching.</p>
<p>For those who are unable to run CURRENT, there is a
backported patch to 10.2-RELEASE.</p>
- <p>Thanks to everyone who helped in the process, I couldn't
+ <p>Thanks to everyone who helped in the process. I couldn't
have done it without you (you know who you are).
</p>
@@ -285,7 +285,7 @@
</project>
<project cat='kern'>
- <title>Cavium LiquidIO Smart NIC driver</title>
+ <title>Cavium LiquidIO Smart NIC Driver</title>
<contact>
<person>
@@ -314,8 +314,8 @@
<p>This project aims to add support for the LiquidIO family
of high-performance programmable accellerator 10/40-gigabit
Ethernet network adapters. The currently developed kernel driver
- supports CN6640- and CN6880-based PCIe cards, enabling the
- following features:</p>
+ supports CN6640- and CN6880-based PCIe cards, enabling these
+ features:</p>
<ul>
<li>A CNNIC API for controlling/interacting with the smart NIC
@@ -340,11 +340,11 @@
</li>
<li>Sysctl-based device statistics and configuration view</li>
<li>Custom firmware loading via user-built modules and
- &os;'s firmware(9) mechanism.</li>
+ &os;'s <tt>firmware(9)</tt> mechanism.</li>
</ul>
<p>The project is currently being developed in house and is
- currently being prepared for upstream. We plan on making it
+ being prepared for upstream. We plan on making it
available in &os; 11.</p>
</body>
@@ -394,7 +394,7 @@
respective branches, among other things.</p>
<p>In mid-August, the &os; Release Engineering Team
- released &os; 10.2-RELEASE, two weeks earlier than the
+ released &os; 10.2-RELEASE two weeks earlier than the
original schedule anticipated.</p>
<p>The &os; Release Engineering Team would like to thank
@@ -412,7 +412,7 @@
</project>
<project cat='proj'>
- <title>Porting bhyve to ARM-based platforms</title>
+ <title>Porting <tt>bhyve</tt> to ARM-based Platforms</title>
<contact>
<person>
@@ -438,12 +438,12 @@
</links>
<body>
- <p>This summer we've started porting bhyve onto ARMv7
- platforms. We rewrote the low-level routines for ARM processors,
+ <p>This summer we have started porting <tt>bhyve</tt> onto ARMv7
+ platforms. The low-level routines for ARM processors were rewritten
while trying to preserve the hypervisor API originally created for
the x86 architectures. We managed to bring up a &os; guest up to
the point of initializing interrupts. There is still work to be
- done in order to virtualize the interrupts and the timer. As
+ done in order to virtualize the interrupts and the timer. Our
short-term plan after finishing the interrupts and the timer is
porting to a real hardware platform (Cubie2).
</p>
@@ -491,7 +491,7 @@
<links>
<url href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=202468">PR
- for the new Port</url>
+ for the new port</url>
<url href="https://github.com/t-zuehlsdorff/gitlabhq/blob/master/doc/install/installation-freebsd.md">Installation
guide</url>
<url href="https://github.com/gitlabhq/gitlabhq/">GitLab
@@ -504,19 +504,19 @@
and Alibaba. It also is a very long-standing entry on the
"Wanted Ports" list on the &os; Wiki.</p>
- <p>In the last month there was steady progress, which finally
- resulted in the PR for adding the new port. In addition to the
+ <p>In the last month there was steady progress, finally
+ resulting in the PR for adding the new port. In addition to the
many dependencies &a.pgollucci; is working on, there was already a
- large amount of work done. In addition to many new or updated
- rubygems, Rails 4.1 was resurrected. Many committers were
+ large amount of work done. Along with many new or updated
+ rubygems, Rails 4.1 was resurrected. A large group of committers were
involved in the process and guided us through the various problems
and pitfalls.</p>
<p>Because of the number of dependencies — we nearly hit
100 — making progress takes some time. In the meantime,
- there is already a new major version of GitLab released, which
- requires even more dependencies and updates. Work on this version
- is already in progress, but the first goal is to get the latest
+ a new major version of GitLab has already been released,
+ requiring even more dependencies and updates. Work on this version
+ is in progress, but the first goal is to get the latest
stable version from the 7.14 branch into the ports tree.
</p>
</body>
@@ -535,7 +535,7 @@
</task>
<task>
- <p>Update the port to the latest version of the 8.x branch</p>
+ <p>Updating the port to the latest version of the 8.x branch</p>
</task>
</help>
</project>
@@ -622,13 +622,13 @@
<body>
<p>Node.js is a platform built on Chrome's JavaScript runtime
- for easily building fast, scalable, network applications. It uses
+ for easily building fast, scalable network applications. It uses
an event-driven, non-blocking I/O model that makes it lightweight
and efficient, perfect for data-intensive real-time applications
that run across distributed devices.</p>
<p>The goal of this project is to make it easy to install the
- modules available on the <a href="http://npmjs.org/">npm package
+ modules available in the <a href="http://npmjs.org/">npm package
registry</a>.</p>
<p>Currently, the repository contains more than 100 new ports,
@@ -649,17 +649,17 @@
<help>
<task>
- <p>Bring in grunt.js (and modules), the JavaScript task runner.</p>
+ <p>Bring in <tt>grunt.js</tt> (and modules), the JavaScript task runner.</p>
</task>
<task>
- <p>Put more effort into support of node-gyp in the USES
+ <p>Put more effort into support of <tt>node-gyp</tt> in the USES
framework</p>
</task>
</help>
</project>
<project cat='proj'>
- <title>Root remount</title>
+ <title>Root Remount</title>
<contact>
<person>
@@ -677,23 +677,23 @@
</links>
<body>
- <p>One of the long missing features of FreeBSD was the ability
+ <p>A feature long missing from &os; was the ability
to boot up with a temporary rootfs, configure the kernel to
be able to access the real rootfs, and then replace the
temporary root with the real one.
In Linux, the functionality is known as pivot_root.
- The reroot projects aims to provide similar functionality in
- a different, slightly more user-friendly way: rerooting.
- Simply put, from the user point of view it's as simple as
- running "reboot -r", which makes the system perform a partial
+ The reroot project aims to provide similar functionality in
+ a different, slightly more user-friendly way.
+ Simply put, from the user point of view it is as simple as
+ running <tt>reboot -r</tt>. The system performs a partial
shutdown, killing all processes and unmounting the rootfs,
and then partial bringup, mounting the new rootfs, running
init, and running the startup scripts as usual.</p>
- <p>The kernel part of the project was committed to 11-CURRENT.
- The userland part is at "finishing touches" stage, and is
+ <p>The kernel part of the project has been committed to 11-CURRENT.
+ The userland part is at the "finishing touches" stage, and is
expected to be committed soon.
- A merge to stable/10 is planned and reroot support should
+ A merge to stable/10 is planned and reroot support is planned
be included in &os; 10.3.</p>
</body>
@@ -703,7 +703,7 @@
</project>
<project cat='proj'>
- <title>Clang, llvm, lldb, compiler-rt and libc++ updated to 3.7.0</title>
+ <title>Clang, <tt>llvm</tt>, <tt>lldb</tt>, <tt>compiler-rt</tt> and <tt>libc++</tt> Updated to 3.7.0</title>
<contact>
<person>
@@ -744,16 +744,16 @@
<body>
- <p>We have updated clang, llvm, lldb, compiler-rt and libc++
+ <p>We have updated <tt>clang</tt>, <tt>llvm</tt>, <tt>lldb</tt>, <tt>compiler-rt</tt> and <tt>libc++</tt>
in base to 3.7.0 release.
- These all contain numerous improvements; please see the linked
+ These all contain numerous improvements. Please see the linked
release notes for more detailed information.
This brings us completely up-to-date with the latest upstream
versions of these projects. Meanwhile, &a.emaste; is working
- on importing the llvm.org version of libunwind.</p>
+ on importing the llvm.org version of <tt>libunwind</tt>.</p>
<p>Like the 3.5.x and 3.6.x releases, these components require
- C++11 support to build. At this point, FreeBSD 10.0 and later
+ C++11 support to build. At this point, &os; 10.0 and later
provide that support, at least on x86.
Currently, there are no solid plans to MFC these versions to
any stable branches, due to the difficulties this would
@@ -764,14 +764,14 @@
</p>
<p>During the first ports exp-run, some major problems were
- found, one introduced by a clang bug which caused pow() to
- generate floating point exceptions in some cases, which in
- turn caused libpng to fail to build, and one bug in
- libjpeg-turbo, which was caused by undefined behavior.
+ found, one introduced by a <tt>clang</tt> bug which caused <tt>pow()</tt> to
+ generate floating point exceptions in some cases. This in
+ turn caused <tt>libpng</tt> to fail to build, and one bug in
+ <tt>libjpeg-turbo</tt>, which was caused by undefined behavior.
These two problems took some time to fix, after which another
exp-run was done, and this resulted in about a dozen newly
failed ports. For almost all of these new failures, fixes
- were submitted, and linked to the original PR 201377 for
+ were submitted and linked to the original PR 201377 for
the exp-run.</p>
</body>
@@ -810,14 +810,14 @@
<p>A number of UEFI bug fixes were committed over the last
quarter, improving compatibility with different UEFI
implementations.
- This includes improvements to EFI's vt(4) framebuffer
- driver, efifb, to handle systems with high resolution
+ This includes improvements to EFI's <tt>vt(4)</tt> framebuffer
+ driver, <tt>efifb</tt>, to handle systems with high resolution
displays and unusual framebuffer stride values.
- In particular this improves compatibility with a large
+ In particular, this improves compatibility with a large
number of recent Apple MacBook Pros and other Macs.</p>
</body>
<help>
- <task>Test FreeBSD-CURRENT and FreeBSD-STABLE snapshots on
+ <task>Test &os;-CURRENT and &os;-STABLE snapshots on
a variety of UEFI implementations.</task>
</help>
</project>
@@ -841,17 +841,17 @@
</links>
<body>
- <p>The Mesa ports were updated to 10.6.8. At the same time, the
+ <p>The Mesa ports were updated to 10.6.8. At the same time, the
ports received a major overhaul to make sure all ports are
correctly configured.
- Also the dual version support was removed; there is only one
+ Dual version support was removed. There is only one
mesa version for all supported &os; versions.
The libosmesa port was merged into the Mesa framework.</p>
<p>Another big item that was included in the Mesa port is
OpenCL. There are two GPU-based OpenCL implementations:
- lang/clover for supported Radeon cards, and
- lang/beignet for supported Intel cards (currently only
+ <tt>lang/clover</tt> for supported Radeon cards, and
+ <tt>lang/beignet</tt> for supported Intel cards (currently only
Ivybridge).
Thanks go to Johannes Dieterich, O. Hartmann, and Koop Mast
for making this happen.</p>
@@ -859,15 +859,15 @@
<p>Now that Mesa is up-to-date, we can apply the same update
procedure to the X.Org server. It is currently at 1.14,
and an update to 1.17 is ready.
- It should be committed shortly.</p>
+ It will be committed shortly.</p>
<p>On the kernel side, progress has been made with the
i915 update. The driver is able to attach.
- There are some reports that the X.Org server starts, but Mesa
- is unhappy so acceleration does not work yet.
- If you want to test, instructions will be posted on the wiki,
+ There are some reports that the X.Org server starts but Mesa
+ is unhappy, so acceleration does not work yet.
+ If you want to test, instructions will be posted on the wiki
in the i915 update article (see links).
- At this stage, we can only accept patches, though — we won't be
+ At this stage, we can only accept patches, though — we will not be
able to provide support.</p>
<p>We attended two conferences: XDC 2015 in Toronto and
@@ -878,7 +878,7 @@
<help>
<task>
- <p>See the "Graphics" wiki page for up-to-date information.</p>
+ <p>See the Graphics wiki page for up-to-date information.</p>
</task>
</help>
</project>
@@ -979,7 +979,7 @@
venue, and getting the T-shirts made.</p>
<p>Benedict helped organize, and he and &a.dru; participated
- in, the
+ in the
<url href="https://wiki.freebsd.org/201507DevSummit">&os;
Hackathon</url> in the Linuxhotel in Essen, Germany.
It was a successful weekend of fixing bugs and collaborating
@@ -1009,7 +1009,7 @@
and participants would learn how to contribute documentation
to the Project.</p>
- <p>We continued to publish our monthly newsletters keeping the
+ <p>We continued to publish our monthly newsletters, keeping the
community informed on what we are doing including event
recaps, testimonials, project updates, and upcoming events.
We received testimonials from Microsoft, NYCBus, and
@@ -1051,21 +1051,21 @@
and marketing literature.</p>
<p>We met with commercial users to get their input on what
- they’d like to see supported in &os;.
+ they would like to see supported in &os;.
We also do this to help connect &os; developers with
commercial users to help facilitate collaboration.</p>
- <p>&os; Foundation employee and Release Engineer, &a.gjb;,
+ <p>&os; Foundation employee and Release Engineer &a.gjb;
was extremely busy during this quarter, working on a number
of exciting areas of the &os; Project.
Some of the highlights include:
<ul>
<li>Code cleanup and bug fixes to several parts of the
- release build code, and finished adding support for
+ release build code, and finishing adding support for
automatically uploading cloud provider images, which was
merged to the stable/10 branch before the code freeze.
The 10.2-RELEASE cycle spanned a 9-week timeframe overall,
- from the start of the code slush.</li>
+ starting from the code slush.</li>
<li> With the &os; Release Engineering Team, released two
BETA builds and three RC builds for the 10.2-RELEASE
cycle, with the final release announced mid-August,
@@ -1125,22 +1125,22 @@
infrastructure to validate that a number of the network stack's
multiqueue behaviours are functioning as expected.</p>
- <p>At present, most parts of this project have been
+ <p>At present, most of this project has been
implemented. It mainly consists of two parts:</p>
<ol>
<li>A general mechanism to collect the per-ring per-cpu
statistics that can be used by all NIC drivers, and extensions to
- netstat(1) to report these statistics.</li>
+ <tt>netstat(1)</tt> to report these statistics.</li>
<li>A suite of network stack behavior testing programs that consists
of:
<ul>
- <li>a virtual multiqueue ethernet interface (vme)</li>
- <li>a UDP packet generator based on vme</li>
- <li>a UDP server based on socket(2)</li>
- <li>a TCP client based on lwip and vme</li>
- <li>a TCP server based on socket(2).</li>
+ <li>a virtual multiqueue ethernet interface (<tt>vme</tt>)</li>
+ <li>a UDP packet generator based on <tt>vme</tt></li>
+ <li>a UDP server based on <tt>socket(2)</tt></li>
+ <li>a TCP client based on <tt>lwip</tt> and <tt>vme</tt></li>
+ <li>a TCP server based on <tt>socket(2)</tt>.</li>
</ul>
</li>
</ol>
@@ -1181,7 +1181,7 @@
<p>This quarter, GNOME 3.16 and MATE 1.10 were committed to the
ports tree, followed up by some incremental improvements. A
chapter covering the use of USE_GNOME within individual ports'
- Makefiles was written and committed to the porters handbook.</p>
+ <tt>Makefile</tt>s was written and committed to the Porter's Handbook.</p>
<p>GNOME 3.18 has been ported. There are, however, some issues
that need to be resolved before it can be committed to the
@@ -1191,13 +1191,13 @@
<help>
<task>
- <p>The GNOME website is stale. Work is underway to improve
+ <p>The GNOME website is stale. Work is under way to improve
it.</p>
</task>
<task>
<p>Please give feedback on and suggest improvements to the
- chapter in the Porters handbook on the <tt>USE_GNOME</tt>
+ chapter in the Porter's Handbook on the <tt>USE_GNOME</tt>
functionality.</p>
</task>
@@ -1291,17 +1291,17 @@
memory model and algorithms expressed with C11 atomics can be
trivially reused under &os;.</p>
- <p>One facility of C11 that was missing from &os; atomics,
- was fences. Fences are bidirectional barrier operations
+ <p>One facility of C11 that was missing from &os; atomics
+ was <em>fences</em>. Fences are bidirectional barrier operations
which could not be expressed by the existing atomic+barrier
accesses. They were added in r285283.</p>
<p>Due to the strong memory model implemented by x86 processors,
- atomic_load_acq() and atomic_store_rel() can be implemented by
- plain load and store instructions with only a compiler barrier; no
+ <tt>atomic_load_acq()</tt> and <tt>atomic_store_rel()</tt> can be implemented by
+ plain load and store instructions with only a compiler barrier. No
additional ordering constraints are required. This simplification
- of atomic_store_rel() was done some time ago in r236456. The
- atomic_load_acq() change was done in r285934, after careful review
+ of <tt>atomic_store_rel()</tt> was done some time ago in r236456. The
+ <tt>atomic_load_acq()</tt> change was done in r285934, after careful review
of all its uses in the kernel and user-space to ensure that no
hidden dependency on a stronger implementation was left.</p>
@@ -1318,7 +1318,7 @@
dependencies. The corresponding optimization was committed in
r284901.</p>
- <p>The atomic(9) man page was often a cause of confusion due to
+ <p>The <tt>atomic(9)</tt> man page was often a cause of confusion due to
both erroneous and ambiguous statements. The most significant of
these issues were addressed in changes r286513 and r286784.</p>
@@ -1381,7 +1381,7 @@
</contact>
<links>
- <url href="https://wiki.freebsd.org/riscv">FreeBSD
+ <url href="https://wiki.freebsd.org/riscv">&os;
wiki RISC-V</url>
<url href="https://people.freebsd.org/~br/riscv-singleuser.txt">Single
user boot log</url>
@@ -1440,8 +1440,8 @@
<p>Over the past several weeks, 26 ports that were indeed
broken on at least PowerPC had been fixed, 58 ports that were
- incorrectly marked as broken (left-overs from the old times) were
- unmarked, and fewer than 40 ports still have issues requiring
+ incorrectly marked as broken (leftovers from the old times) were
+ marked as working, and fewer than 40 ports still have issues requiring
further work.
</p>
</body>
@@ -1449,7 +1449,7 @@
<help>
<task>
<p>The Ports Collection could benefit a lot from more frequent sweeps
- targetting Tier-2 systems.</p>
+ targeting Tier-2 systems.</p>
</task>
<task>
@@ -1489,7 +1489,7 @@
project had initially been advised would make it illegal
for him to contribute. After several years, Core was asked to
revisit the issue. On the advice of counsel, Core decided that
- it could restore commit privileges to commmitters resident in
+ it could restore commit privileges to commmitters residing in
Iran.</p>
<p>The CTM service came under security review. Given that the lack of
@@ -1502,7 +1502,7 @@
<p>Core learned that ISC was ceasing its hosting service, which has
entailed a rapid rework of plans on the movement of significant
- portions of the &os; cluster to that datacentre. Cluster
+ portions of the &os; cluster to that data center. Cluster
administration has taken ownership of the situation and is making
progress.</p>
@@ -1575,7 +1575,7 @@
<p>On the QA side, 25 exp-runs were performed to validate
sensitive updates or cleanups. Amongst those, the noticeable
changes are the update to <tt>pkg</tt> 1.6, the <tt>automake14</tt>
- removal, and several important ports updates such as
+ removal, and several important port updates such as
<tt>doxygen</tt> to 1.8.10, <tt>gnome3</tt> to 3.16,
<tt>cmake</tt> to 3.3.1, and the Qt4 ports to 4.8.7. The default
jdk was also set to <tt>openjdk8</tt>. Some infrastructure
@@ -1594,7 +1594,7 @@
reports cannot seem to stop increasing. So if you use ports or
packages, please consider jumping in and helping! This is also
true for existing porters: it would be great if you would consider
- the next step, that is to share your knowledge and mentor someone
+ the next step, which is to share your knowledge and mentor someone
more junior with the ports tree internals. And if you already do
these tasks, many thanks to you!
</p>
@@ -1667,7 +1667,7 @@
<ul>
<li>The cluster runs a mixture of 11-current and 10-stable
as part of our "eat our own dogfood" project. For this
- to be useful we do monthly cluster refreshes to keep up with
+ to be useful, we do monthly cluster refreshes to keep up with
current code.</li>
<li>We build internal base system snapshots every few days
and packages every day.</li>
@@ -1721,18 +1721,18 @@
Berner (area51)</li>
<li>Updated qt5 to 5.5.0. Ralf Nolden has contributed a
- handful of usefull new ports, for example lang/qt5-l10n
- (area51/qt-5.5)</li>
+ handful of useful new ports, for example <tt>lang/qt5-l10n</tt>
+ (<tt>area51/qt-5.5</tt>)</li>
- <li>The plasma5 branch has been kept up to date with KDE's
+ <li>The <tt>plasma5</tt> branch has been kept up to date with KDE's
upstream and contains ports for Frameworks 5.14.0, Plasma Desktop
- 5.4.2 and Applications 15.08.1 (area51/plasma5)</li>
+ 5.4.2 and Applications 15.08.1 (<tt>area51/plasma5</tt>)</li>
</ul>
</body>
<help>
<task>
- <p>Work on getting the stuff from plasma5 branch into ports.
+ <p>Work on getting the stuff from <tt>plasma5</tt> branch into ports.
(This is a major update to nearly all KDE applications, so
testers are very welcome.)</p>
</task>
@@ -1774,11 +1774,11 @@
</links>
<body>
- <p>On arm64, numerous cleanups and fixes have been applied to
- the kernel. This includes fixes to exception handling,
+ <p>Numerous cleanups and fixes have been applied to
+ the arm64 kernel. This includes fixes to exception handling,
asynchronous signals, ddb, and pmap. ddb has been updated to
better handle accessing memory that may be unmapped. The pmap
- code was made more complete by implementng more functions as
+ code was made more complete by implementing more functions as
needed.</p>
<p>Further work on SMP means that &os; now boots on all 48
@@ -1786,7 +1786,7 @@
support for the ARM GICv3 interrupt controllers and fixing the
memory mapping to be shareable between CPUs.</p>
- <p>The test suite has been run on both qemu, and hardware. Most of the
+ <p>The test suite has been run on both qemu and hardware. Most of the
test cases are passing, with around 30 tests either broken or failing.
Work on diagnosing the issues with the remaining test cases is ongoing.
</p>
@@ -1808,7 +1808,7 @@
</project>
<project cat="arch">
- <title>&os; on the HiKey ARMv8 board</title>
+ <title>&os; on the HiKey ARMv8 Board</title>
<contact>
<person>
@@ -1836,7 +1836,7 @@
USB host, and will boot off the SD card to multi-user mode using
a recent arm64 snapshot.</p>
- <p>The kernel is missing a number of device drivers, however, it is at
+ <p>The kernel is missing a number of device drivers. However, it is at
a usable state for people interested in testing &os; on ARMv8
hardware.
</p>
@@ -2033,18 +2033,18 @@
</project>
<project cat='bin'>
- <title>pkg 1.6</title>
+ <title><tt>pkg</tt> 1.6</title>
<contact>
<person>
- <name>&os; pkg Team</name>
+ <name>&os; <tt>pkg</tt> Team</name>
<email>pkg at FreeBSD.org</email>
</person>
</contact>
<body>
<p><tt>pkg</tt> 1.6.0 has been released. Many changes
- have been made since pkg 1.5:</p>
+ have been made since <tt>pkg</tt> 1.5:</p>
<ul>
<li>The dependency solver is greatly improved</li>
@@ -2053,17 +2053,17 @@
in the dependency line</li>
<li><tt>pkg check -d</tt> now also checks the required libraries</li>
<li>Improved support for partial upgrades</li>
- <li>Improved zsh completion support</li>
- <li>Improved Linux support (all regression tests now pass on
- Linux)</li>
- <li>Messages can now be context aware, only printing a given
- message during installation, upgrade (conditional on
- previous version), removal, or always</li>
+ <li>Improved <tt>zsh</tt> completion support</li>
+ <li>Improved Linux support: all regression tests now pass on
+ Linux</li>
+ <li>Messages can now be context aware, showing a given
+ message always, or only during installation, upgrade (conditional on
+ previous version), or removal</li>
<li>@keywords now accept new entries to add context-aware messages</li>
<li>Added the ability to generate graphiz's dot format
representation of the solver's problem</li>
- <li><tt>pkg search</tt> now defaults to showing the pkg-comments
- of of the matched packages</li>
+ <li><tt>pkg search</tt> now defaults to showing the <tt>pkg-comments<//t>
+ of the matched packages</li>
<li>Lots of bug fixes and code cleanup</li>
<li>Improvements in cross-installation support</li>
</ul>
@@ -2071,13 +2071,13 @@
<help>
<task>
- <p>Add a notion of priority to the list of files so as to
- ensure that certain files are the first to be replaced
- (a blocker for packaging base).</p>
+ <p>Add a notion of priority to the list of files to
+ ensure that certain files are the first to be replaced.
+ This was a blocker for packaging base.</p>
</task>
<task>
- <p>Investigate replacing openssl by mbedtls.</p>
+ <p>Investigate replacing <tt>openssl</tt> by <tt>mbedtls</tt>.</p>
</task>
</help>
</project>
@@ -2120,13 +2120,13 @@
currently being worked on. Support for running &os; as an amd64
Xen host (Dom0) is available in HEAD.</p>
- <p>On the x86 front most of the Xen work during this quarter
- was focused on reworking the implementation of PVH inside of the
- Xen hypervisor, so most of the activity during this quarter
+ <p>On the x86 front, most of the work during this quarter
+ focused on the implementation of PVH inside
+ Xen. Consequently, most of the activity
happened inside of the hypervisor. Patches for a clean PVH
implementation have been posted, with the aim of having them
- merged in the next Xen release (4.7). Once that's done, work will
- continue on adding new features to both &os; and Xen in order to
+ merged in the next Xen release (4.7). Once that is done, work will
+ continue on adding new features to both &os; and Xen to
have feature parity with traditional PV guests/hosts.</p>
<p>Apart from this, work is ongoing to import a new netfront
@@ -2134,8 +2134,8 @@
channel and multiple queue support.</p>
<p>On the ARM front, this quarter's work focused on getting
- &os;/arm64 booting as Xen guest. The current activity is to
- upstream patches preparing Xen drivers to support arm64; this
+ &os;/arm64 booting as a Xen guest. The current activity is to
+ upstream patches preparing Xen drivers to support arm64. This
includes a rework of the console driver.</p>
</body>
@@ -2165,7 +2165,7 @@
</project>
<project cat='proj'>
- <title>bhyve</title>
+ <title><tt>bhyve</tt></title>
<contact>
<person>
@@ -2229,16 +2229,16 @@
<p>A combined <tt>bhyve</tt> and ZFS BoF was held during vBSDCon 2015,
hosted by Michael Dexter and Allan Jude. Questions asked about
- <tt>bhyve</tt> were live migration and suspend/resume support, and
+ <tt>bhyve</tt> included live migration and suspend/resume support, and
configurations using ZFS.</p>
- <p>Three bhyve-related project were selected for GSoC 2015:
+ <p>Three <tt>bhyve</tt>-related projects were selected for GSoC 2015:
NE2000 device emulation, porting <tt>bhyve</tt> to ARM, and
ptnetmap support.</p>
<p>The major enhancement for <tt>bhyve</tt> this quarter was
- support for an external firmware, along with a port of the Intel
- edk2 UEFI firmware. This allows bhyve to run Windows in headless
+ support for external firmware, along with a port of the Intel
+ edk2 UEFI firmware. This allows <tt>bhyve</tt> to run Windows in headless
mode, and also Illumos.</p>
<ul>
@@ -2286,7 +2286,7 @@
</task>
<task>
- <p>Live Migration.</p>
+ <p>Live migration.</p>
</task>
<task>
@@ -2300,7 +2300,7 @@
</project>
<project cat='proj'>
- <title>High Availability clustering in CTL</title>
+ <title>High Availability Clustering in CTL</title>
<contact>
<person>
@@ -2317,7 +2317,7 @@
Copan/SGI, had support for High Availability clustering.
Unfortunately, significant portions of the HA code were never
published with the main body of the source code. Now, the missing
- part has been reimplemented from scratch and fixed/improved.</p>
+ part has been reimplemented from scratch, fixed, and improved.</p>
<p>This code supports dual-node HA with Asynchronous LUN Unit
Access (ALUA) in four modes:</p>
@@ -2325,28 +2325,28 @@
<ul>
<li>Active/Unavailable without interlink between nodes, where
the secondary node can report nothing except its presence.</li>
- <li>Active/Standby with secondary node handling only basic LUN
+ <li>Active/Standby with the secondary node handling only basic LUN
discovery and reservation, synchronizing state and command
execution with the primary node through the interlink.</li>
<li>Active/Active with both nodes processing commands and
accessing the backing storage, synchronizing state and command
execution with the primary node through the interlink.</li>
- <li>Active/Active with secondary node having no backing storage
- access, but instead working as a proxy, transfering all commands
+ <li>Active/Active with the secondary node having no backing storage
+ access, but instead working as a proxy, transferring all commands
to the first node for execution through the interlink.</li>
</ul>
<p>In the case of lost interlink connectivity to primary node,
the secondary node falls into the Transitioning state, which is
- like Unavailable and can't answer most requests, but makes the
+ like Unavailable and cannot answer most requests, but makes the
initiator wait for recovery or cluster failover.</p>
<p>CTL also got a large number of other improvements, including
support for emulation of CD/DVD drives and removable disks,
- live LUN reconfiguration, etc.</p>
+ live LUN reconfiguration, and so on.</p>
<p>The code is committed to &os; head and was recently merged to
- stable/10 branch.
+ the stable/10 branch.
</p>
</body>
@@ -2356,7 +2356,7 @@
</project>
<project cat='proj'>
- <title>ZFS Code Sync With Latest Illumos</title>
+ <title>ZFS Code Sync with Latest Illumos</title>
<contact>
<person>
@@ -2369,8 +2369,8 @@
</contact>
<body>
- <p>The ZFS codebase got significant batch of merges, and is
- now in sync with latest Illimos. Among other things, this update
+ <p>The ZFS codebase received a significant batch of merges, and is
+ now in sync with latest Illumos. Among other things, this update
includes:</p>
<ul>
@@ -2378,7 +2378,7 @@
<li>Improved prefetch for faster send/receive.</li>
<li>Reduced RAM usage by almost 50% for L2ARC.</li>
<li>Improved I/O aggregation.</li>
- <li>Fine-grained checksuming in send/receive stream.</li>
+ <li>Fine-grained checksumming in send/receive stream.</li>
<li>Reduced import time for pools with many datasets.</li>
<li>Reworked and simplified predictive prefetcher.</li>
</ul>
@@ -2390,7 +2390,7 @@
</project>
<project cat='bin'>
- <title>mandoc and roff Toolchain</title>
+ <title><tt>mandoc</tt> and <tt>roff</tt> Toolchain</title>
<contact>
<person>
@@ -2414,39 +2414,38 @@
manual pages.</p>
<p><tt>mandoc</tt> is the default renderer for manpages on
- &os; head. This quarter, the apropos(1) utility was switched to
- use mandoc's version, which offers a new database format (in
- sqlite) bringing more powerful, fine-grained ways to search
- manpages.</p>
+ &os; head. This quarter, the <tt>apropos(1)</tt> utility was switched to
+ use <tt>mandoc</tt>'s version, which offers a new database format (in
+ SQLite) bringing more powerful, fine-grained ways to search
+ man pages.</p>
- <p>While mandoc is very good for manpages, we also provide
+ <p>While <tt>mandoc</tt> is very good for man pages, we also provide
lots of other documentation in plain <tt>roff</tt> format. The
- heirloom toolchain is being studied to replace <tt>groff</tt> in
- base. The heirloom nroff toolchain has multiple benefits: it has
- very good unicode support, and very good compatibility with
- groff.</p>
-
- <p>A great deal of work as been done testing the heirloom
- nroff toolchain with all the roff documents in the base system
- (including manpages), and upstream has been very proactive in
+ Heirloom toolchain is being studied to replace <tt>groff</tt> in
+ base. The Heirloom <tt>nroff</tt> toolchain has multiple benefits: it has
+ very good unicode support and very good compatibility with
+ <tt>groff</tt>.</p>
+
+ <p>A great deal of work as been done testing the Heirloom
+ <tt>nroff</tt> toolchain with all the <tt>roff</tt> documents in the base system
+ (including man pages), and upstream has been very proactive in
fixing reported bugs.</p>
- <p>The 'soelim(1)' utility has been replaced with a
+ <p>The <tt>soelim(1)</tt> utility has been replaced with a
BSD-licensed version which is good enough to work with all available
- roff toolchains (to ease transition). This version
- of the soelim(1) utility, originally written solely for &os;, is
- now part of the mandoc tool suite.</p>
+ <tt>roff</tt> toolchains to ease the transition. This version
+ of the <tt>soelim(1)</tt> utility, originally written solely for &os;, is
+ now part of the <tt>mandoc</tt> tool suite.</p>
- <p>The col(1) utility has been cleaned up and updated to
+ <p>In coordination with Ingo Schwarze from OpenBSD, the <tt>col(1)</tt> utility has been cleaned up and updated to
recognize both SUSv2-style escape-digit and BSD-style
- escape-control-char sequences in the input stream (in coordination
- with Ingo Schwarze from OpenBSD)</p>
+ escape-control-char sequences in the input stream.</p>
- <p>The checknr(1) utility has been cleaned up and extended to
- support modern roff(7) macros (including synchronizing code from NetBSD
- and the heirloom docutils version).</p>
+ <p>The <tt>checknr(1)</tt> utility has been cleaned up and extended to
+ support modern <tt>roff(7)</tt> macros, including synchronizing code from NetBSD
+ and the Heirloom docutils version.</p>
- <p>Many roff fixes were made to documentation and manpages,
+ <p>Many <tt>roff</tt> fixes were made to documentation and man pages,
having been discovered while testing the new toolchain.
</p>
</body>
@@ -2491,18 +2490,18 @@
<help>
<task>
- <p>Test the libkvm changes on platforms other than amd64, i386,
+ <p>Test the <tt>libkvm</tt> changes on platforms other than amd64, i386,
and powerpc64.</p>
</task>
<task>
- <p>Figure out why the powerpc kgdb targets are not able to unwind
+ <p>Figure out why the powerpc <tt>kgdb</tt> targets are not able to unwind
the stack past the initial frame.</p>
</task>
<task>
<p>Add support for more platforms (arm, mips, aarch64) to
- upstream gdb for both userland and kgdb.</p>
+ upstream <tt>gdb</tt> for both userland and <tt>kgdb</tt>.</p>
</task>
<task>
@@ -2517,7 +2516,7 @@
</project>
<project cat='bin'>
- <title>truss(1)</title>
+ <title><tt>truss(1)</tt></title>
<contact>
<person>
@@ -2538,30 +2537,30 @@
</contact>
<body>
- <p>The interface between the ABI-specific backends and the truss
+ <p>The interface between the ABI-specific backends and the <tt>truss</tt>
core was refactored, reducing duplicated code. This prompted
additional follow-on work to add support for more ABIs, including
aarch64 and CloudABI.</p>
- <p>In addition, ptrace(2) was extended to return more
+ <p><tt>ptrace(2)</tt> was extended to return more
information about the currently executing system call. This
- restored behavior that had been present in a previous verison of
- truss of knowing the correct number of arguments for all system
+ restored behavior that had been present in a previous version of
+ <tt>truss</tt>: knowing the correct number of arguments for all system
calls.</p>
- <p>The fork-following support in truss was reworked to use
- native fork following in ptrace(2) rather than forking a new truss
+ <p>The fork-following support in <tt>truss</tt> was reworked to use
+ native fork following in <tt>ptrace(2)</tt> rather than forking a new <tt>truss</tt>
process for each child of a traced process.</p>
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
More information about the svn-doc-all
mailing list