svn commit: r50245 - head/en_US.ISO8859-1/htdocs/news/status
Benjamin Kaduk
bjk at FreeBSD.org
Wed May 10 03:10:19 UTC 2017
Author: bjk
Date: Wed May 10 03:10:17 2017
New Revision: 50245
URL: https://svnweb.freebsd.org/changeset/doc/50245
Log:
Make an editing pass through the 2017Q1 report
Modified:
head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml
Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml Tue May 9 23:31:05 2017 (r50244)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml Wed May 10 03:10:17 2017 (r50245)
@@ -98,27 +98,24 @@
<body>
<p>Work has started on an initial translation of the &os;
- Handbook to the Dutch language via the 'po' system. While we
+ Handbook to the Dutch language via the "po" system. While we
have an (outdated) version of the Handbook available via the
older XML files, we are now trying to get back into shape with
the po file.</p>
<p>Rene started working on 2 articles already and did some
- translation strings for the FDP-Primer, while Remko had started
- working on the Handbook. If you think you can assist with that,
- please let Rene and Remko know on their email addresses so that
+ translation of strings for the FDP-Primer, while Remko has started
+ working on the Handbook. If you think you can assist with either,
+ please send Rene and Remko an email so that
we can start coordinating work.</p>
<p>In addition, since we have a translation set already from the
XML files, it would be interesting to see and know whether we
can merge them easily into the po structure. If you have ideas
on that, contact us a.s.a.p.</p>
-
- <p>Part of this work is facilitated by Remko's employer:
- Snow B.V.</p>
</body>
- <sponsor>Snow B.V.</sponsor>
+ <sponsor>Snow B.V. (in part)</sponsor>
<help>
<task>Identify a way to merge the current XML translations into
@@ -126,13 +123,13 @@
<task>Merge the translations into the .po files.</task>
- <task>Update the remaining/open items into the po files.</task>
+ <task>Update the remaining open items into the po files.</task>
<task>Remove the old/outdated translation files from the main
- repo and use the po and book.xml files to generate the dutch
+ repo and use the <tt>po</tt> and <tt>book.xml</tt> files to generate the Dutch
handbook and other files.</task>
- <task>Identify whether we can also translate the htdocs pages
+ <task>Identify whether we can also translate the <tt>htdocs</tt> pages
via the po system.</task>
</help>
</project>
@@ -153,29 +150,29 @@
<body>
<p>A long time ago, in the &os; 5 times, there was an initial
port of &os; to s390 (32bit) and s390x (64bit)
- which booted past init on good days in an emulator.</p>
+ which booted past <tt>init</tt> on good days in an emulator.</p>
<p>As an attempt to revive the s390x/systemz efforts I started
- to get &os; s390x to build with clang/llvm 3.90.
- At this time it is possible to build world and a GENERIC kernel
+ to get &os; s390x to build with clang/llvm 3.9.
+ At this time, it is possible to build world and a GENERIC kernel
skeleton (not doing anything yet) using external binutils.</p>
- <p>The primary idea of this initial work was to allow to
- incrementally add the neccessary architecture-specific code.
- Having the build framework done will allow third-party
+ <p>The primary idea of this initial work was to allow for
+ incremental addition of the neccessary architecture-specific code.
+ Having the build framework in place will allow third-party
developers to simply type <tt>make</tt>, as they are willing
to contribute to the port without having to know &os; build
specifics. After some cleanup and further updates to a more
recent HEAD I am planning to push the current work to a public
- repo to allow collaboration.</p>
+ repo to facilitate collaboration.</p>
</body>
<help>
<task>Write a wiki page with per-architecture specific tasks
- that need to be done based on the current work and the experience
+ that need to be done, based on the current work and the experience
from arm64 and riscv.</task>
- <task>Implement both the user space and kernel per-architecture
+ <task>Implement both the userspace and kernel per-architecture
gaps.</task>
<task>Figure out a way to get access to IBM's zPDT or better
@@ -225,7 +222,7 @@
<task>Port the dTSEC driver to 64-bit. There are assumptions in the
reference driver of operating in a 32-bit environment. It may
be easier to port the Linux driver instead, which would also
- give ARM support.</task>
+ give ARM support for this ethernet controller.</task>
<task>Take advantage of pointer alignment to squeeze more bits
out of the page tables; it should be possible to squeeze at
@@ -259,11 +256,11 @@
<p>My first attempt at a pNFS server using GlusterFS was a dud.
It worked, but performance was so poor that it was not
- usable. This attempt that I call Plan B, only uses &os;,
- with one &os; server handling the metadata operations and K
+ usable. This attempt that I call "Plan B", only uses &os;,
+ with one &os; server handling the metadata operations and multiple
&os; servers configured to serve data. An NFSv4.1 client
that supports the pNFS File Layout will be able to
- read/write to the data servers directly, spreading out the
+ read and write to the data servers directly, spreading out the
RPC load and allowing growth beyond that of what a single
&os; NFS server could achieve.</p>
@@ -320,7 +317,7 @@
<body>
<p>OpenBSM is a BSD-licensed implementation of Sun's Basic Security
- Module (BSM) API and file format. It is the user space side of the
+ Module (BSM) API and file format. It is the userspace side of the
CAPP Audit implementations in &os; and Mac OS X. Additionally,
the audit trail processing tools are expected to work on Linux.</p>
@@ -332,7 +329,8 @@
In the OpenBSM GitHub repository, support for Coverity static
analysis was added via TravisCI. Additionally, the OpenBSM
1.2-alpha5 release has been merged into the &os; HEAD
- branch.</p> </body>
+ branch.</p>
+ </body>
<help>
<task>Test the latest release on different versions of &os;, Mac OS X
@@ -342,7 +340,7 @@
<task>Fix problems that have been reported via GitHub and the
&os; bug tracker.</task>
- <task>Implement features mentioned in the TODO list on
+ <task>Implement the features mentioned in the TODO list on
GitHub.</task>
</help>
@@ -396,7 +394,7 @@
<p>During this quarter, the TrustedBSD project transitioned from the
&os; Perforce server to GitHub. This was made possible by
- Alexis Sarghel, who owned the user "trustedbsd" on GitHub and
+ Alexis Sarghel, who owned the user "trustedbsd" on GitHub and
graciously transferred this account to the TrustedBSD project.
To date, the repositories hosting the TrustedBSD website and
the SEBSD repository have been moved.</p>
@@ -431,22 +429,22 @@
<body>
<p>This quarter a new <tt>-dev</tt> version of MySQL landed in
- the port tree, MySQL 8.0. It introduces many new features,
+ the Ports Collection, MySQL 8.0. It introduces many new features,
though we had to (re)-patch parts of it which were merged by
MySQL from MySQL5.7.</p>
- <p>We also updated MySQL 5.6 to latest version and closed bunch
- of PRs related to it, mostly about using &os;-provided ports
- for librariess instead of the bundled copies. And of course
+ <p>We also updated MySQL 5.6 to its latest version and closed many
+ PRs related to it, mostly relating to using &os;-provided ports
+ for libraries instead of the bundled copies. And of course
there were plenty of security updates.</p>
<p>We can also report that the problem of having to specify
- <tt>${mysql_optfile}</tt>, which some people encountered while
- using MySQL, is now considered to be solved in all MySQL
- versions: 5.6, 5.7, and 8.0. Now the init script will search
- all default locations, for backwards compatibility with the
- variety of locations used for configuration files before it
- gives up and reports an error.</p>
+ <tt>${mysql_optfile}</tt>, which some people encountered while
+ using MySQL, is now considered to be solved in all MySQL
+ versions: 5.6, 5.7, and 8.0. Now the init script will search
+ all default locations, for backwards compatibility with the
+ variety of locations used for configuration files, before it
+ gives up and reports an error.</p>
</body>
<help>
@@ -484,18 +482,19 @@
</contact>
<body>
- <p>In this quarter, we are pleased to announce two (of many) works achieved in the Linuxulator.</p>
+ <p>In this quarter, we are pleased to announce two (of many)
+ works achieved in the Linuxulator.</p>
<p>We added a new placeholder marker <tt>UNIMPLEMENTED</tt> to
accompany the previously existing <tt>DUMMY</tt>, for
distinguishing syscalls that the Linux kernel itself does not
implement from those that we currently do not implement. Now
- our <tt>linux_dummy.c</tt> is clearer for the newcomers to
+ our <tt>linux_dummy.c</tt> is clearer for newcomers to
follow, and they will quickly know which areas they can start
working on.</p>
- <p>Support for two new syscalls, <tt>preadv</tt> and
- <tt>pwritev</tt>, was added to the Linuxulator.</p>
+ <p>Support for two new syscalls, <tt>preadv</tt> and
+ <tt>pwritev</tt>, was added to the Linuxulator.</p>
</body>
<help>
@@ -613,7 +612,7 @@
<links>
<url href="https://wiki.FreeBSD.org/HyperV">&os; Virtual Machines on Microsoft Hyper-V</url>
- <url href="https://technet.microsoft.com/en-us/library/dn531030.aspx">Supported Linux and &os; virtual machines for Hyper-V on Windows</url>
+ <url href="https://technet.microsoft.com/en-us/library/dn531030.aspx">Supported Linux and &os; Virtual Machines for Hyper-V on Windows</url>
</links>
<body>
@@ -622,7 +621,7 @@
despite some issues (Bug 216493: <a
href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=216493">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=216493</a>).</p>
- <p>Updates for UEFI VMs (i.e., Hyper-V Generation 2 VM):</p>
+ <p>Updates for UEFI VMs (i.e., Hyper-V Generation 2 VMs):</p>
<ol>
<li>After the loader issue (Bug 211746) is fixed, UEFI VMs can
@@ -654,7 +653,7 @@
</contact>
<links>
- <url href="https://nuxi.nl/cloudabi/FreeBSD/">How to use CloudABI on &os;</url>
+ <url href="https://nuxi.nl/cloudabi/FreeBSD/">How to Use CloudABI on &os;</url>
<url href="https://nuxi.nl/blog/2017/02/18/porting-leveldb-to-cloudabi.html">LevelDB for CloudABI</url>
<url href="https://nuxi.nl/blog/2017/03/15/sandboxed-memcached.html">Memcached for CloudABI</url>
<url href="https://laanwj.github.io/2017/03/02/porting-bitcoin-core-to-cloudabi.html">Bitcoin for CloudABI</url>
@@ -674,14 +673,14 @@
<a href="http://www.boost.org/">Boost</a> and
<a href="http://leveldb.org/">LevelDB</a>. Now that these
libraries are readily available, we're at the point where we can
- shift focus towards porting full applications.</p>
+ shift our focus towards porting full applications.</p>
<p>Late February one of the lead developers of
<a href="https://github.com/bitcoin/bitcoin">the Bitcoin reference
implementation</a> got in touch, as he is very interested in
creating a copy of Bitcoin that is better protected against
security bugs. You do not want a security bug in the
- networking/consensus code allowing an attacker to steal coins from
+ networking/consensus code to allow an attacker to steal coins from
your local wallet.</p>
<p>As I think that this is a use case that demonstrates the strength
@@ -711,7 +710,7 @@
</project>
<project cat='team'>
- <title>Ports Collection</title>
+ <title>The &os; Ports Collection</title>
<contact>
<person>
@@ -747,7 +746,7 @@
<p>In the last quarter, we welcomed 7 new committers: Eugene Grosbein
(eugen), Johannes Dieterich (jmd), Larry Rosenman (ler), Mahdi Mokhtari
(mmohki), Matthew Rezny (rezny), Tobias Kortkamp (tobik), and Vladimir
- Krstulja (?). dumbbell@ was already a src committer and got an extension
+ Kondratyev (wulf). dumbbell@ was already a src committer and got an extension
for the Ports Tree. We also welcomed back krion@ and miwi at . We took 6
bits in for safe-keeping: itetcu@, leeym@, mva@, olivierd@, pgollucci@,
and sanpei at .</p>
@@ -758,11 +757,11 @@
removal of the long-outdated Samba 3.6 ports and replace them
with modern versions. The new default versions are:
FreePascal 3.0.2, Ruby 2.3, and Samba 4.4. A new variable
- <tt>USE_LOCALE</tt> was createdto add the <tt>LANG</tt> and
+ <tt>USE_LOCALE</tt> was created to add the <tt>LANG</tt> and
<tt>LC_ALL</tt> environment variables to all builds.
Out-of-tree patches can now be added with the new
<tt>EXTRA_PATCH_TREE</tt> variable. The error messages for
- invalid <tt>SINGLE</tt> options were improved.</p>
+ invalid <tt>OPTIONS_SINGLE</tt> options were improved.</p>
<p>Some of the major port updates last quarter were: pkg 1.10.1, linux
c6_64, Firefox 52.0.2, Chromium 57.0.2987.110, GCC 4.9.4, Gnome 3.18.0,
@@ -845,7 +844,7 @@
</project>
<project cat='team'>
- <title>&os; Release Engineering Team</title>
+ <title>The &os; Release Engineering Team</title>
<contact>
<person>
@@ -862,7 +861,7 @@
<body>
<p>The &os; Release Engineering Team is responsible for setting
and publishing release schedules for official project releases
- of &os;, announcing code freezes and maintaining the
+ of &os;, announcing code freezes, and maintaining the
respective branches, among other things.</p>
<p>The &os; Release Engineering Team continued producing
@@ -874,9 +873,7 @@
the website is still subject to change.</p>
</body>
- <sponsor>
- The &os; Foundation
- </sponsor>
+ <sponsor>The &os; Foundation</sponsor>
</project>
<project cat='arch'>
@@ -903,7 +900,7 @@
<body>
<p>Final testing and productionization of support for the
Marvell Armada38x platform is underway. The rebase and cleanup
- is going well, with support on top of HEAD and ready for
+ is going well, with patches functioning on top of HEAD and ready for
upstreaming.</p>
<p>Specific tasks completed include:</p>
@@ -978,15 +975,15 @@
UEFI code in the boot partition, as is done on some Intel NUCs,
another use case for partition support is the activation of
pseudo-SLC mode, which manufacturers of eMMC chips typically
- associate with the enhanced user data area and/or the enhanced
+ associate with the enhanced user data area and/or the "enhanced"
attribute of general purpose partitions.</p>
<p>In order to be able to partition eMMC devices, r315430 also
- added a Linux-compatible IOCTL interface to <tt>mmcsd(4)</tt>.
- This allows for using the GNU <tt>mmc-utils</tt> (found in ports
+ added a Linux-compatible <tt>ioctl(2)</tt> interface to <tt>mmcsd(4)</tt>.
+ This allows the use of the GNU <tt>mmc-utils</tt> (found in ports
as <tt>sysutils/mmc-utils</tt>) on &os;. Besides partitioning
eMMC devices, the <tt>mmc</tt> tool can also be used to query
- for life time estimate and pre-EOL information of eMMC flash, as
+ for lifetime estimates and pre-EOL information of eMMC flash, as
well as to query some basic information from SD cards.</p>
<p>CAVEAT EMPTOR: Partitioning eMMC devices is a one-time
@@ -995,13 +992,13 @@
<p>Additionally, in order to make eMMC flash devices more
usable, support for DDR (Dual Data Rate) bus speed mode at a
maximum of 52 MHz (DDR52) has been added to <tt>mmc(4)</tt>
- and <tt>sdhci(4)</tt> in r315598, i.e., in &os; 12. Compared
+ and <tt>sdhci(4)</tt> in r315598, which will appear in &os; 12. Compared
to high speed mode (the previous maximum) at 52 MHz, DDR52
mode increases the performance of the tested eMMC chips from
~45 MB/s to ~80 MB/s.</p>
<p>So far, support for DDR52 mode has been enabled for the eMMC
- controllers found in Intel Apollo Lake, Bay Trail and Braswell
+ controllers found in the Intel Apollo Lake, Bay Trail and Braswell
chipsets. Note, however, that the eMMC and SDHCI controllers
of the Apollo Lake variant occasionally lock up due to a
silicon bug (which is independent of running in DDR52 mode).
@@ -1019,7 +1016,7 @@
</body>
<help>
- <task>Add support for eMMC HS200, HS400 and HS400ES transfer
+ <task>Add support for eMMC HS200, HS400, and HS400ES transfer
modes.</task>
<task>Add support for SD card UHS-I transfer modes (SDR12 to
@@ -1079,15 +1076,15 @@
compatibility with legacy applications.</p></li>
</ul>
- <p>I started looking into Ceph, because the HAST solution with
+ <p>I started looking into Ceph because the HAST solution with
CARP and <tt>ggate</tt> did not really do what I was looking
for. But I aim to run a Ceph storage cluster of storage nodes
that are running ZFS. User stations would be running
- <tt>bhyve</tt> on RBD disk that are stored in Ceph.</p>
+ <tt>bhyve</tt> on RBD disks that are stored in Ceph.</p>
<p>The &os; build will build most of the tools in Ceph.</p>
- <p>The most notable progress since the last report:</p>
+ <p>Notable progress since the last report:</p>
<ul>
<li>The most important change is that a port has been
@@ -1156,12 +1153,12 @@
<task>Scheduler information is not used at the moment, because the
schedulers work rather differently between Linux and &os;.
But at a certain point in time, this will need some attention
- (in src/common/Thread.cc).</task>
+ (in <tt>src/common/Thread.cc</tt>).</task>
- <task>Improve the &os; initscripts in the Ceph stack, both for
+ <task>Improve the &os; init scripts in the Ceph stack, both for
testing purposes and for running Ceph on production machines.
Work on <tt>ceph-disk</tt> and <tt>ceph-deploy</tt> to make it
- more &os;- and ZFS- compatible.</task>
+ more &os;- and ZFS-compatible.</task>
<task>Build a test cluster and start running some of the
teuthology integration tests on it. Teuthology wants to build
@@ -1197,7 +1194,7 @@
<p>Unfortunately, this quarter we had an instance where such private
measures failed to achieve the desired result, and we ended up
- ejecting a developer. John Marino is an extremely talented
+ ejecting a developer. This developer is an extremely talented
programmer and has made significant contributions to the Ports
Collection. Despite this, portmgr found him to be
sufficiently disruptive and abrasive that in their judgement,
@@ -1210,7 +1207,7 @@
<p>In a more positive light, Core has been working on a proposal
to recognise notable contributors to the &os; project who are not
(or perhaps <i>not yet</i>) suitable to be put forward as new
- committers. In addition to the usual routes of recognising people
+ committers. In addition to the usual routes of recognising people
that write numbers of good bug reports or that supply patches or
that volunteer to maintain ports, this will also allow recognition
of people who contribute by such things as organising &os; events
@@ -1220,8 +1217,8 @@
<p>During January, the core secretary held an exercise to contact
all source committers who had been inactive for more than 18
months and persuade them to hand in their commit bits if they
- weren't planning to resume working on &os; in the near future.
- This is meant to be a routine function -- the "grim reaper" --
+ were not planning to resume working on &os; in the near future.
+ This is meant to be a routine function -- the "grim reaper" --
that aims to keep the list of people with the ability to commit
pretty much in synchrony with the list of people that are actively
committing. The regular process had fallen out of activity
@@ -1236,10 +1233,10 @@
important &os; users would be keen to see it happen, given some of
the work that has gone into the stable/10 branch since
10.3-RELEASE. On the other hand, this would require an additional
- support burden for SecTeam, including maintaining versions of
+ support burden for the Security Team, including maintaining versions of
software that have been declared obsolete upstream, in particular
OpenSSL. As an even-numbered release, 10.4-RELEASE would have a
- "normal" rather than an "extended" lifetime which means it should
+ "normal" rather than an "extended" lifetime which means it should
not result in extending the support lifetime of the stable/10
branch.</p>
@@ -1261,8 +1258,8 @@
<p>Core is looking for new volunteers to help out with several of
the teams that manage various aspects of the project. In
- particular, Postmaster and SecTeam are in need of new blood.
- Recruiting a new member of SecTeam is well underway, but anyone
+ particular, Postmaster and the Security Team are in need of new blood.
+ Recruiting for a new member of the Security Team is well underway, but anyone
interested in joining any of the teams is encouraged to make
themselves known either to Core, or directly to the teams
concerned.</p>
@@ -1270,7 +1267,7 @@
</project>
<project cat="kern">
- <title>MMC Stack Under CAM Framework</title>
+ <title>MMC Stack Using the CAM Framework</title>
<contact>
<person>
@@ -1295,14 +1292,14 @@
generated by the inserted card, which is a prerequisite for
implementing the SDIO interface. SDIO support is necessary
for communicating with the WiFi/BT modules found on many
- development boards, like Raspberry Pi 3.</p>
+ development boards, like the Raspberry Pi 3.</p>
<p>Another feature that the new stack will have is support for
sending SD commands from userland applications using
<tt>cam(3)</tt>. This will allow for building device drivers in
userland and make debugging much easier.</p>
- <p>The new stack is able to attach to the SD card and bring it
+ <p>The new stack is able to attach to an SD card and bring it
to an operational state so that it is possible to read and
write to the card.</p>
@@ -1312,17 +1309,17 @@
<p>Currently the code is being prepared for inclusion in the
&os; source tree. <tt>cam(3)</tt> is being extended to
support SDIO-specific functions (reading registers, managing
- interrupts).</p>
+ interrupts, etc.).</p>
</body>
<help>
<task>Integrate the code into &os; HEAD to facilitate
testing.</task>
- <task>Begin writing driver for Broadcom-based WLAN chips (found
+ <task>Begin writing a driver for Broadcom-based WLAN chips (found
on the Raspberry Pi 3 and Wandboard).</task>
- <task>Begin writing driver for Marvell-based WLAN chips (found
+ <task>Begin writing a driver for Marvell-based WLAN chips (found
on the GlobalScale Dreamplug and some Chromebooks).</task>
</help>
</project>
@@ -1362,7 +1359,7 @@
arrangements that require a recognized legal entity.</p>
<p>Our work is 100% funded by your donations. We kicked off the
- new year with some large contributions from Intel and NetApp,
+ new year with some large contributions from Intel and NetApp,
to help us raise over $400,000 last quarter! We engaged in
discussions with new and old commercial users to help
facilitate collaboration, explain how the Project works, and
@@ -1374,7 +1371,7 @@
<p>The Foundation improves the &os; operating system by
employing our technical staff to maintain and improve critical
kernel subsystems, add features and functionality, and fix
- problems. This also includes funding separate project grants
+ problems. Our contributions also include funding separate project grants
like the arm64 port, <tt>blacklistd</tt> access control
daemon, and integration of <tt>VIMAGE</tt> support, to make
sure &os; remains a viable solution for research, education,
@@ -1387,11 +1384,11 @@
tree (base system) development branch, across three staff
members and four grant recipients/other developers.</li>
- <li>Funded grants including the <tt>cfumass</tt> project, now
+ <li>Multiple funded grants, including the <tt>cfumass</tt> project, now
committed to &os;-HEAD, and improvements to the
<tt>blacklistd</tt> daemon and &os;/arm64 port.</li>
- <li>Staff contributions including improvements to tool chain
+ <li>Staff contributions including improvements to toolchain
and build tool components, run time libraries, arm64, mips64
and 32- and 64-bit x86 architectures, release image build
tooling, packaged base, and VM subsystem bug fixes.</li>
More information about the svn-doc-all
mailing list