From owner-svn-doc-all@freebsd.org Wed May 10 03:10:18 2017
Return-Path: 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. 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. 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. Part of this work is facilitated by Remko's employer:
- Snow B.V. 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.
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.
-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 +
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 make, 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.
+ repo to facilitate collaboration.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.
@@ -320,7 +317,7 @@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.
@@ -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. + branch. +This quarter a new -dev 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.
-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 +
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.
We can also report that the problem of having to specify - ${mysql_optfile}, 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.
+ ${mysql_optfile}, 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.