svn commit: r49170 - head/en_US.ISO8859-1/htdocs/news/status
Benjamin Kaduk
bjk at FreeBSD.org
Tue Jul 26 04:36:20 UTC 2016
Author: bjk
Date: Tue Jul 26 04:36:19 2016
New Revision: 49170
URL: https://svnweb.freebsd.org/changeset/doc/49170
Log:
Another round of edits to the 2016Q2 report
Modified:
head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml
Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml Tue Jul 26 02:18:57 2016 (r49169)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2016-04-2016-06.xml Tue Jul 26 04:36:19 2016 (r49170)
@@ -98,12 +98,12 @@
<p>The &os; Release Engineering Team completed the 10.3-RELEASE
cycle late April, led by &a.marius;. The release was one week
behind the original schedule, to accommodate for a few
- last-minute critical issues that were essential to include in the
+ last-minute critical issues that were essential to fix in the
final release.</p>
<p>The &os; 11.0-RELEASE cycle started late May, one month
behind the original schedule. The schedule slip was primarily
- to accommodate for packaging the &os; base system with the
+ to accommodate efforts for packaging the &os; base system with the
<tt>pkg(8)</tt> utility. However, as work on this progressed,
it became apparent that there were too many outstanding
issues. As a result, packaged base will be a "beta" feature
@@ -145,7 +145,7 @@
<p>While there is ongoing progress to remove Rails 3.2 from
the ports tree, there are some ports for which this is a major
- update that block the overall process. The most recent blocker
+ update that blocks the overall process. The most recent blocker
was the outstanding update of <tt>www/redmine</tt> from 2.6 to
3.2. This has completed successfully, so we can now move on.</p>
@@ -271,10 +271,10 @@
POSIX threads implementation, <tt>libthr</tt>,
the only major feature lacking for POSIX compliance is robust
mutexes. Robust mutexes allow applications to detect, and
- theoretically, recover from crashes which occur while
+ theoretically recover from, crashes which occur while
modifying the shared state. The supported model is to protect
shared state by a <tt>pthread_mutex</tt>, and the crash is
- detected as the thread termination while owning the mutex. A
+ detected as thread termination while owning the mutex. A
thread might terminate alone, or it could be killed due to the
termination of the containing process. As such, the robust
attribute is applicable to both process-private and -shared
@@ -282,7 +282,7 @@
<p>An application must be specifically modified to handle and
recover from failures. The <tt>pthread_mutex_lock()</tt>
- function may return new error <tt>EOWNERDEAD</tt>, which
+ function may return a new error <tt>EOWNERDEAD</tt>, which
indicates that the previous owner of the lock terminated while
still owning the lock. Despite returning this non-zero value,
the lock is granted to the caller. In the simplest form, an
@@ -291,7 +291,7 @@
reinitialization. More sophisticated applications could try
to automatically recover from the condition, in which case
<tt>pthread_mutex_consistent(3)</tt> must be called on the
- lock before the unlock. However, such recovery can be
+ lock before unlocking it. However, such recovery can be
considered to be very hard. Still, even the detection of
inconsistent shared state is useful, since it avoids further
corruption and random faults of the affected application.
@@ -747,8 +747,9 @@
complete the full test suite without errors.</li>
</ol>
- <p>11-CURRENT is used to compile and build test Ceph. The
- Clang toolset needs to be at least version 3.7, as Clang 3.4
+ <p>11-CURRENT is used to compile and build-test Ceph. The
+ Clang toolset needs to be at least version 3.7, as the Clang 3.4
+ available on stable/10
does not have all of the capabilities required to compile
everything.</p>
@@ -801,7 +802,7 @@
<li>CephFS: Cython tries to access an internal field in
<tt> struct dirent</tt>, which fails to compile.</li>
- <li>Tests that verify the correct functionality of these are
+ <li>Tests that verify the correct functionality of these features are
also excluded from the test suite.</li>
</ul>
@@ -824,7 +825,7 @@
</body>
<help>
- <task>The current and foremost task it to get the test suite to
+ <task>The current and foremost task is to get the test suite to
complete without errors.</task>
<task>Build an automated test platform that will build
@@ -842,7 +843,7 @@
<task>Get the currently excluded Python tests to work.</task>
- <task>Compile and test the user space RBD (Rados Block
+ <task>Compile and test the userspace RBD (Rados Block
Device).</task>
<task>Investigate if an in-kernel RBD device could be developed
@@ -878,7 +879,7 @@
<body>
<p>After being in the &os; Ports Collection for three months,
GitLab continues to mature and gain adoption. Most of its
- starting problems have been resolved, with one known issue
+ initial problems have been resolved, with one known issue
left: it does not start on boot. Any help in solving this
issue is welcome.</p>
@@ -914,8 +915,8 @@
</links>
<body>
- <p>This is an interim report on the technical state of the ASLR
- patch.</p>
+ <p>This is an interim report on the technical state of my
+ work towards ASLR support in the &os; base system.</p>
<p>The <tt>proccontrol(1)</tt> utility was written to manage and
query ASLR enforcement on a per-process basis. It is required
@@ -940,7 +941,7 @@
<p><tt>-q</tt> (queries the state of the specified mode for the
process with the PID specified by the <tt>-p</tt> option)</p>
- <p><tt>-e</tt> (toggles the feature on or off for the given
+ <p><tt>-s</tt> (toggles the feature on or off for the given
process or itself)</p>
<p>If a command is specified, it inherits the applied
@@ -980,11 +981,11 @@
attempting to override memory from other allocators.</p>
<p>&os; uses the <tt>MAP_EXCL</tt> flag to <tt>mmap(2)</tt>,
- which must be used in the <tt>MAP_FIXED|MAP_EXCL</tt> form to
+ which must be used in the form <tt>MAP_FIXED|MAP_EXCL</tt> to
cause <tt>mmap(2)</tt> to fail if the requested range is
already used. I tried to force <tt>MAP_FIXED</tt> requests
from SBCL to implicitly set <tt>MAP_EXCL</tt>, but this did
- not go well since SBCL sometimes pre-allocates regions for
+ not go well, since SBCL sometimes pre-allocates regions for
later use with <tt>MAP_FIXED</tt>. So, <tt>MAP_EXCL</tt>
mappings failed, dumping the process into <tt>ldb</tt>.</p>
@@ -1203,7 +1204,7 @@
quarters:</p>
<ul>
- <li>Registration of &os; Group Contacts (GC) with freenode
+ <li>Registered &os; Group Contacts (GC) with freenode
staff. For information on what this means, see <a
href="https://freenode.net/groupreg">the group
registration page</a>.</li>
@@ -1309,7 +1310,7 @@
term.</p>
<p>It is critical to have a strong developer presence amongst
- users and IRC Admin would like to call on all developers to
+ users, and IRC Admin would like to call on all developers to
join the &os; freenode channels to help support that
presence. We are the &os; giants on whose shoulders the
future contributors stand. It is important to be there, in
@@ -1590,7 +1591,7 @@
importantly, their <strong>states</strong>. Another example
is ensuring that various flags and keywords are unambiguous
and well understood. For instance, "patch" and
- "patch-ready", can often be misunderstood or
+ "patch-ready" can often be misunderstood or
misapplied.</li>
<li>Issue statistics are lacking, and for the next quarter we
@@ -1712,7 +1713,7 @@
<body>
<p>Reproducible builds are a set of software development
- practices which create a verifiable path from human readable
+ practices which create a verifiable path from human-readable
source code to the binary code used by computers. In brief,
the idea is that building the same binary, software package,
document, or other binary artifact twice from the same source
@@ -1926,7 +1927,7 @@
<body>
<p>The <tt>arm64 pmap</tt> code has been updated to work with
the full 4 pagetable levels. This allows us to increase the
- user virtual address space to 256TB, with an increase of the
+ user virtual address space to 256TB, with a concomittant increase of the
kernel virtual address space. It also allows an increase in
the size of the physical memory &os; can handle to up to
2TB.</p>
@@ -2059,7 +2060,7 @@
quarter: added filesystem thoughput limits to RCTL; committed iSER
initiator support; added support for rerooting into NFS; and added
<tt>iscsictl -e</tt>, which makes it possible to enable and disable
- sessions.</p>
+ iSCSI sessions.</p>
<p>Ed Maste, our Project Development Director, accomplished
the following work last quarter: investigated the state of
@@ -2144,7 +2145,7 @@
<p>We also published monthly newsletters to highlight work being
done to support &os;, tell you about upcoming events, and provide
- other information to keep you in the loop of what we're doing to
+ other information to keep you in the loop on what we're doing to
support the &os; Project and community.</p>
<p>George Neville-Neil and Robert Watson continued teaching
@@ -2229,7 +2230,7 @@
see the Foundation support, and other input to help us determine
our direction and how we should support the Project.</p>
- <p>Code of Conduct — Anne Dickison, our Marketing Director,
+ <p>Anne Dickison, our Marketing Director,
has been overseeing the efforts to rewrite the Project's Code of
Conduct to help make this a safe, inclusive, and welcoming
community.</p>
More information about the svn-doc-all
mailing list