Date: Fri, 20 Jan 2017 22:12:22 +0000 (UTC) From: Warren Block <wblock@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r49875 - head/en_US.ISO8859-1/htdocs/news/status Message-ID: <201701202212.v0KMCMJ0069365@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: wblock Date: Fri Jan 20 22:12:22 2017 New Revision: 49875 URL: https://svnweb.freebsd.org/changeset/doc/49875 Log: Whitespace-only fixes, translators please ignore. Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml Fri Jan 20 21:41:10 2017 (r49874) +++ head/en_US.ISO8859-1/htdocs/news/status/report-2016-10-2016-12.xml Fri Jan 20 22:12:22 2017 (r49875) @@ -116,26 +116,26 @@ <p>&os; 11.0-RELEASE shipped with support for the "enhanced networking" support in EC2 C3, C4, R3, I2, D2, and M4 - (excluding m4.16xlarge) instances. This provides significantly - higher network performance than the virtual networking - available on older EC2 instances and with older versions of - &os;.</p> + (excluding m4.16xlarge) instances. This provides + significantly higher network performance than the virtual + networking available on older EC2 instances and with older + versions of &os;.</p> <p>&os; 11.0-RELEASE and later also use indirect segment disk - I/Os, which yield approximately 20% higher throughput with equal or lower - latency, and support the 128-vCPU x1.32xlarge instance - type.</p> + I/Os, which yield approximately 20% higher throughput with + equal or lower latency, and support the 128-vCPU x1.32xlarge + instance type.</p> <p> &os; now supports the Amazon Simple Systems Manager service ("run command").</p> </body> <help> - <task>Complete a pending reorganization of the accounts used for &os;/EC2 - releases.</task> + <task>Complete a pending reorganization of the accounts used for + &os;/EC2 releases.</task> - <task>Support "second generation enhanced networking" via - the new Elastic Network Adapter found in P2, R4, X1, and + <task>Support "second generation enhanced networking" + via the new Elastic Network Adapter found in P2, R4, X1, and m4.16xlarge instances.</task> <task>Provide tools for improved functionality via the Simple @@ -143,8 +143,8 @@ for updates, adding/removing users, [your favourite sysadmin task goes here].</task> - <task>Add support for EC2's IPv6 networking to the default &os;/EC2 - configuration.</task> + <task>Add support for EC2's IPv6 networking to the default + &os;/EC2 configuration.</task> <task>Continue ongoing interoperability testing between &os;'s NFS client and Amazon Elastic File System @@ -173,33 +173,34 @@ <body> <p>Prometheus is an Open Source monitoring system that was - originally built at SoundCloud in 2012. Since 2016, this project is - part of the Cloud Native Computing Foundation, together with other - projects like Kubernetes.</p> - - <p>Prometheus scrapes its targets by periodically sending HTTP GET - requests. Targets then respond by sending key-value pairs of metrics - and their sample value. Prometheus has a query language, PromQL, - that can be used to aggregate sample values and specify alerting - conditions. Tools like Grafana can be used to create fancy - dashboards using such queries.</p> + originally built at SoundCloud in 2012. Since 2016, this + project is part of the Cloud Native Computing Foundation, + together with other projects like Kubernetes.</p> + + <p>Prometheus scrapes its targets by periodically sending HTTP + GET requests. Targets then respond by sending key-value pairs + of metrics and their sample value. Prometheus has a query + language, PromQL, that can be used to aggregate sample values + and specify alerting conditions. Tools like Grafana can be + used to create fancy dashboards using such queries.</p> <p>The Prometheus project provides a utility called the - node_exporter that gathers basic system metrics and serves them - over HTTP. This utility tends to be rather complex, as it has - to extract metrics from many different sources. On Linux, files - in <tt>/proc</tt> have no uniform format, meaning that for every - kernel framework a custom collector needs to be written.</p> + node_exporter that gathers basic system metrics and serves + them over HTTP. This utility tends to be rather complex, as + it has to extract metrics from many different sources. On + Linux, files in <tt>/proc</tt> have no uniform format, meaning + that for every kernel framework a custom collector needs to be + written.</p> <p>On &os; the sitiuation is better, as the data exported - through <tt>sysctl</tt> is already structured in such a way that - it can easily be translated to Prometheus' metrics format. The - goal of this project is thus to provide a generic exporter for - the entire sysctl tree. Not only does this prevent unnecessary - bloat and indirection, it may also make the life of a kernel - developer a lot easier. One can easily use Prometheus to graph - the occurrence of an event over time by (temporarily) adding a - counter to the kernel.</p> + through <tt>sysctl</tt> is already structured in such a way + that it can easily be translated to Prometheus' metrics + format. The goal of this project is thus to provide a generic + exporter for the entire sysctl tree. Not only does this + prevent unnecessary bloat and indirection, it may also make + the life of a kernel developer a lot easier. One can easily + use Prometheus to graph the occurrence of an event over time + by (temporarily) adding a counter to the kernel.</p> <p>An initial version of the sysctl exporter has been integrated into the &os; base system in December. It can be run through @@ -215,14 +216,14 @@ exporter a try!</task> <task>It would be nice if we created a set of useful alerting - rules and placed those in /usr/share/examples. For example, how - can one use this exporter to monitor the state of GEOM-based - RAID arrays? Is such information even exported through - <tt>sysctl</tt>?</task> + rules and placed those in /usr/share/examples. For example, + how can one use this exporter to monitor the state of + GEOM-based RAID arrays? Is such information even exported + through <tt>sysctl</tt>?</task> <task>Prometheus uses a pretty nifty format for exporting - histograms. Histograms are useful for expressing the amount of - time taken to complete certain events (for example, disk + histograms. Histograms are useful for expressing the amount + of time taken to complete certain events (for example, disk operations). Would it be possible to add histograms as native datatypes to sysctl? If so, is there any chance they can be implemented without picking up any kernel locks?</task> @@ -249,10 +250,10 @@ <body> <p>The changes necessary to support the Allwinner Consumer IR - interface in &os; have been committed. The receive (RX) side is - supported now and the driver is using the <tt>evdev</tt> - framework. It was tested on the Cubieboard2 (A20 SoC) using - <tt>lirc</tt> with dfrobot's simple IR remote controller.</p> + interface in &os; have been committed. The receive (RX) side + is supported now and the driver is using the <tt>evdev</tt> + framework. It was tested on the Cubieboard2 (A20 SoC) using + <tt>lirc</tt> with dfrobot's simple IR remote controller.</p> </body> </project> @@ -287,7 +288,7 @@ originally developed as part of &os;. It supports a wide variety of input and output formats and also includes three command-line tools: <tt>bsdcat</tt>, <tt>bsdcpio</tt> and - <tt>bsdtar</tt>. The &os; <tt>tar</tt> and <tt>cpio</tt> + <tt>bsdtar</tt>. The &os; <tt>tar</tt> and <tt>cpio</tt> utilities are taken directly from Libarchive, and many other important utilities like <tt>ar</tt>, <tt>unzip</tt>, and the <tt>pkg</tt> package manager make use of <tt>libarchive</tt>'s @@ -296,9 +297,9 @@ <p>Libarchive development in 2016 has been focusing on bug fixes and code cleanup, including fixing several critical security issues. Automated testing with Travis CI and Jenkins has been - introduced and <tt>libarchive</tt> has been added to the Google - OSS-Fuzz project. Fuzzing helped detect several hidden problems - like buffer overflows and memory leaks.</p> + introduced and <tt>libarchive</tt> has been added to the + Google OSS-Fuzz project. Fuzzing helped detect several hidden + problems like buffer overflows and memory leaks.</p> <p>Over the last few months, NFSv4 ACL support for the pax and restricted pax (the default for <tt>bsdtar</tt>) formats has @@ -308,12 +309,13 @@ <help> <task>More extensive CI testing with &os; on different platforms - and releases. Currently only 11.0-RELEASE-amd64 gets tested via - an automated Jenkins job.</task> + and releases. Currently only 11.0-RELEASE-amd64 gets tested + via an automated Jenkins job.</task> <task>As every commit to libarchive may influence the build - process of &os; ports, the ability to trigger a (semi-)automated - exp-run for the ports tree would be great.</task> + process of &os; ports, the ability to trigger a + (semi-)automated exp-run for the ports tree would be + great.</task> </help> </project> @@ -369,7 +371,7 @@ depends on, was implemented.</p> <p>PCIe pass-through is implemented, and the patches to - implement NIC SR-IOV are being reviewed on Phabricator.</p> + implement NIC SR-IOV are being reviewed on Phabricator.</p> <p>vDSO support for speeding up <tt>gettimeofday(2)</tt> is now implemented.</p> @@ -380,8 +382,8 @@ image.</p> <p>We fixed an issue where SCSI disks would sometimes fail to - attach, resolving bug 215171 ([Hyper-V] Fail to attach SCSI disk - from LUN 8 on Win2008R2/Win2012/Win2012R2).</p> + attach, resolving bug 215171 ([Hyper-V] Fail to attach SCSI + disk from LUN 8 on Win2008R2/Win2012/Win2012R2).</p> </body> <sponsor> @@ -415,8 +417,8 @@ <p>7.12 includes additional fixes related to tracing <tt>vfork()</tt>s. Some of these fixes depend on changes to - <tt>ptrace()</tt> in the kernel to report a new ptrace stop when - the parent of a <tt>vfork()</tt> resumes.</p> + <tt>ptrace()</tt> in the kernel to report a new ptrace stop + when the parent of a <tt>vfork()</tt> resumes.</p> <p>Support for &os;/mips userland binaries has been committed upstream. These patches, along with support for debugging @@ -438,7 +440,8 @@ <task>Implement 'info os' commands.</task> - <task>Debug <tt>gdb</tt> hangs related to the 'kill' command.</task> + <task>Debug <tt>gdb</tt> hangs related to the 'kill' + command.</task> </help> </project> @@ -482,36 +485,50 @@ to <tt>x11/qterminal</tt> 0.7.0):</p> <ul> - <li><tt>devel/lxqt-build-tools</tt></li> - - <li><tt>devel/liblxqt</tt></li> - - <li><tt>devel/qtxdg</tt></li> - - <li><tt>x11/libfm-qt</tt></li> + <li> + <tt>devel/lxqt-build-tools</tt> + </li> + <li> + <tt>devel/liblxqt</tt> + </li> + <li> + <tt>devel/qtxdg</tt> + </li> + <li> + <tt>x11/libfm-qt</tt> + </li> </ul> <p>Standalone applications:</p> <ul> - <li><tt>graphics/lximage-qt</tt></li> - - <li><tt>x11-fm/pcmanfm-qt</tt></li> + <li> + <tt>graphics/lximage-qt</tt> + </li> + <li> + <tt>x11-fm/pcmanfm-qt</tt> + </li> </ul> <p>We also have updates for:</p> <ul> - <li><tt>x11/qterminal</tt> 0.7.1</li> - <li><tt>x11-toolkits/qtermwidget</tt> 0.7.1</li> - <li>Updating the Porter's Handbook for LXQt support (<a - href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=215650">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=215650</a>)</li>; + <li> + <tt>x11/qterminal</tt> 0.7.1 + </li> + <li> + <tt>x11-toolkits/qtermwidget</tt> 0.7.1 + </li> + <li> + Updating the Porter's Handbook for LXQt support + (<a href="https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=215650">https://bugs.FreeBSD.org/bugzilla/show_bug.cgi?id=215650</a>) + </li> </ul> </body> <help> - <task>Improve support in <tt>sysutils/lxqt-admin</tt> (especially - date and time settings).</task> + <task>Improve support in <tt>sysutils/lxqt-admin</tt> + (especially date and time settings).</task> </help> </project> @@ -536,57 +553,77 @@ lightweight, while still being visually appealing and easy to use.</p> - <p>During this quarter, the team has kept these applications up-to-date:</p> + <p>During this quarter, the team has kept these applications + up-to-date:</p> <ul> - <li><tt>audio/xfce4-mpc-plugin</tt> 0.5.0 (committed in devel - repository)</li> - - <li><tt>deskutils/xfce4-notifyd</tt> 0.3.4</li> - - <li><tt>graphics/ristretto</tt> 0.8.1</li> - - <li><tt>sysutils/xfce4-diskperf-plugin</tt> 2.6.0</li> - - <li><tt>sysutils/xfce4-battery-plugin</tt> 1.1.0 (committed in - devel repository)</li> - - <li><tt>sysutils/xfce4-fsguard-plugin</tt> 1.1.0 (committed in - devel repository)</li> - - <li><tt>sysutils/xfce4-netload-plugin</tt> 1.3.0 (committed in - devel repository)</li> - - <li><tt>sysutils/xfce4-systemload-plugin</tt> 1.2.0 (committed - in devel repository)</li> - - <li><tt>sysutils/xfce4-wavelan-plugin</tt> 0.6.0 (committed in - devel repository)</li> - - <li><tt>x11/xfce4-clipman-plugin</tt> 1.4.1</li> - - <li><tt>x11/xfce4-conf</tt> 4.12.1</li> - - <li><tt>x11/xfce4-dashboard</tt> 0.6.1</li> - - <li><tt>x11/xfce4-terminal</tt> 0.8.2</li> - - <li><tt>x11/xfce4-whiskermenu-plugin</tt> 1.6.2</li> - - <li><tt>x11-clocks/xfce4-datetime-plugin</tt> 0.7.0 (committed - in devel repository)</li> - - <li><tt>x11-wm/xfce4-panel</tt> 4.12.1</li> - - <li><tt>www/xfce4-smartbookmark-plugin</tt> 0.5.0 (committed - in devel repository)</li> + <li> + <tt>audio/xfce4-mpc-plugin</tt> 0.5.0 (committed in devel + repository) + </li> + <li> + <tt>deskutils/xfce4-notifyd</tt> 0.3.4 + </li> + <li> + <tt>graphics/ristretto</tt> 0.8.1 + </li> + <li> + <tt>sysutils/xfce4-diskperf-plugin</tt> 2.6.0 + </li> + <li> + <tt>sysutils/xfce4-battery-plugin</tt> 1.1.0 (committed in + devel repository) + </li> + <li> + <tt>sysutils/xfce4-fsguard-plugin</tt> 1.1.0 (committed in + devel repository) + </li> + <li> + <tt>sysutils/xfce4-netload-plugin</tt> 1.3.0 (committed in + devel repository) + </li> + <li> + <tt>sysutils/xfce4-systemload-plugin</tt> 1.2.0 (committed + in devel repository) + </li> + <li> + <tt>sysutils/xfce4-wavelan-plugin</tt> 0.6.0 (committed in + devel repository) + </li> + <li> + <tt>x11/xfce4-clipman-plugin</tt> 1.4.1 + </li> + <li> + <tt>x11/xfce4-conf</tt> 4.12.1 + </li> + <li> + <tt>x11/xfce4-dashboard</tt> 0.6.1 + </li> + <li> + <tt>x11/xfce4-terminal</tt> 0.8.2 + </li> + <li> + <tt>x11/xfce4-whiskermenu-plugin</tt> 1.6.2 + </li> + <li> + <tt>x11-clocks/xfce4-datetime-plugin</tt> 0.7.0 (committed + in devel repository) + </li> + <li> + <tt>x11-wm/xfce4-panel</tt> 4.12.1 + </li> + <li> + <tt>www/xfce4-smartbookmark-plugin</tt> 0.5.0 (committed + in devel repository) + </li> </ul> <p>We also follow the unstable releases (available in our experimental repository) of:</p> <ul> - <li><tt>sysutils/xfce4-settings</tt> 4.13.0 (it requires Gtk+ > 3.20)</li> + <li><tt>sysutils/xfce4-settings</tt> 4.13.0 (it requires Gtk+ + > 3.20)</li> <li><tt>x11/libexo</tt> 0.11.2</li> <li><tt>x11/xfce4-whiskermenu-plugin</tt> 2.0.3</li> </ul> @@ -594,8 +631,9 @@ <help> <task>Apply the changes discussed in - <a href="https://reviews.FreeBSD.org/D8416">D8416</a>; (simplify the - <tt>MASTER_SITES</tt> macro in port Makefiles)</task> + <a href="https://reviews.FreeBSD.org/D8416">D8416</a>; + (simplify the <tt>MASTER_SITES</tt> macro in port + Makefiles)</task> <task>Commit the stable panel plugins</task> </help> @@ -639,28 +677,28 @@ <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 CAPP Audit implementations in &os; and Mac OS X. - Additionally, the audit trail processing tools are expected to - work on Linux.</p> + Security Module (BSM) API and file format. It is the + user-space 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> <p>This quarter saw increased development activity, fueled by - the DARPA CADETS project, resulting in the release of OpenBSM 1.2 - alpha 5. Among this release's changes are the ability to + the DARPA CADETS project, resulting in the release of OpenBSM + 1.2 alpha 5. Among this release's changes are the ability to specify the kernel's maximum audit queue length, sandboxing support for <tt>auditreduce(1)</tt> and <tt>praudit(1)</tt> on &os; and other systems that support Capsicum, as well as the addition of event identifiers for more &os; system calls. The - complete list of changes is documented in the <a - href="https://github.com/openbsm/openbsm/blob/master/NEWS">NEWS</a>; + complete list of changes is documented in the + <a href="https://github.com/openbsm/openbsm/blob/master/NEWS">NEWS</a>; file on GitHub. The new release will be merged into &os; HEAD and the supported STABLE branches shortly.</p> - </body> + </body> <help> <task>Test the new release on different versions of &os;, Mac OS - X, and Linux. In particular, testing on the latest versions of Mac - OS X would be greatly appreciated.</task> + X, and Linux. In particular, testing on the latest versions + of Mac OS X would be greatly appreciated.</task> <task>Fix problems that have been reported via GitHub and the &os; bug tracker.</task> @@ -686,51 +724,52 @@ </contact> <body> - <p>The major concern for Core during the last quarter of 2016 has - been about maintaining the effectiveness of secteam. The team is - primarily in need of better project management, both to improve - communication generally and to allow the other team members to - concentrate on the technical aspects of handling + <p>The major concern for Core during the last quarter of 2016 + has been about maintaining the effectiveness of secteam. The + team is primarily in need of better project management, both + to improve communication generally and to allow the other team + members to concentrate on the technical aspects of handling vulnerabilities.</p> <p>To that end, there has been agreement in principle for either the FreeBSD Foundation or one of the companies that are major &os; users to employ someone specifically in this role.</p> - <p>Core confirmed that the new support model would go into effect - with 11.0-RELEASE despite the postponement of the switch to a - packaged base release mechanism. For details of the new support - model, please follow the links from the <a - href="https://www.FreeBSD.org/security/security.html">security</a>; + <p>Core confirmed that the new support model would go into + effect with 11.0-RELEASE despite the postponement of the + switch to a packaged base release mechanism. For details of + the new support model, please follow the links from the + <a href="https://www.FreeBSD.org/security/security.html">security</a>; page of the &os; website.</p> <p>Core requested the removal of the <tt>misc/jive</tt> port, on - the grounds that it had no function other than to turn text into - an offensively racist parody. This proved controversial, with - many seeing this as a first step in bowdlerizing the entire ports - tree. That is certainly not Core's intention. Core's aim here is - to help secure the future of the &os; project by making it - welcoming to all contributors, regardless of ethnicity, gender, - sexuality or other improper bases for discrimintation. While - <tt>misc/jive</tt> may once have been seen as harmless fun, today - the implicit approval implied by having it in the ports tree sends - a message at odds with the project's aims.</p> + the grounds that it had no function other than to turn text + into an offensively racist parody. This proved controversial, + with many seeing this as a first step in bowdlerizing the + entire ports tree. That is certainly not Core's intention. + Core's aim here is to help secure the future of the &os; + project by making it welcoming to all contributors, regardless + of ethnicity, gender, sexuality or other improper bases for + discrimintation. While <tt>misc/jive</tt> may once have been + seen as harmless fun, today the implicit approval implied by + having it in the ports tree sends a message at odds with the + project's aims.</p> <p>The Marketing team and the associated marketing@FreeBSD.org - mailing list were wound up, due to lack of activity. Messages to - marketing@FreeBSD.org will be forwarded to the - FreeBSD Foundation's marketing team instead.</p> + mailing list were wound up, due to lack of activity. Messages + to marketing@FreeBSD.org will be forwarded to the FreeBSD + Foundation's marketing team instead.</p> - <p>Core member Allan Jude, who was already the clusteradm liason, - became a full member of clusteradm.</p> + <p>Core member Allan Jude, who was already the clusteradm + liason, became a full member of clusteradm.</p> <p>An emergency correction to the 11.0 release notes was authorised, as it was giving the misleading impression that 802.11n wireless support had only just been added, and this - misapprehension was being repeated in the press. In reality, &os; - has had 802.11n support for many years, and the announcement - should have said that support had been added to many additional - device drivers.</p> + misapprehension was being repeated in the press. In reality, + &os; has had 802.11n support for many years, and the + announcement should have said that support had been added to + many additional device drivers.</p> <p>Discussions about a proposal to improve Unicode support are on-going. &os; is already standards conformant, but the @@ -739,48 +778,63 @@ Opinions are divided on the technical merits of the new approach.</p> - <p>There were the usual quota of queries about licensing and other - legal matters:</p> + <p>There were the usual quota of queries about licensing and + other legal matters:</p> <ul> - <li>Plans to create a GPLv3 overlay for the base system were + <li> + Plans to create a GPLv3 overlay for the base system were shelved in the light of faster than expected progress at - enabling building the world using an external toolchain.</li> + enabling building the world using an external + toolchain. + </li> - <li>The trademarks page on the website was updated to show the + <li> + The trademarks page on the website was updated to show the current owners of a number of trademarks in their approved - form.</li> + form. + </li> - <li>In the absense of a tool to extract and summarize all of the - relevant information, the obligation in the BSD license that - "Redistributions in binary form must reproduce the above - copyright notice, this list of conditions and the following - disclaimer in the documentation and/or other materials provided - with the distribution." is fulfilled by providing a tarball of - the system sources with their embedded copyright - statements.</li> + <li> + In the absense of a tool to extract and summarize all of + the relevant information, the obligation in the BSD license + that "Redistributions in binary form must reproduce the + above copyright notice, this list of conditions and the + following disclaimer in the documentation and/or other + materials provided with the distribution." is fulfilled + by providing a tarball of the system sources with their + embedded copyright statements. + </li> - <li>The European Court of Justice's "Right to be + <li> + The European Court of Justice's "Right to be Forgotten" only applies to search engines, and the &os; - project is not one of those, so need not take any action.</li> + project is not one of those, so need not take any + action. + </li> - <li>Core is following closely discussions within the LLVM + <li> + Core is following closely discussions within the LLVM project regarding a change of license which if implemented, - might require an audit of the - entire ports tree to discover all packages that contain binaries - linked against libc++ and ensure that they are licensed - compatibly with LLVM. However, indications are that the LLVM - project will not adopt such changes.</li> - - <li>The "Open Source Exception" in the firmware - license means that committing a "binary blob" driver - for the Nvidia Jetson TK1 XHCI device is acceptable.</li> + might require an audit of the entire ports tree to discover + all packages that contain binaries linked against libc++ and + ensure that they are licensed compatibly with LLVM. + However, indications are that the LLVM project will not + adopt such changes. + </li> + + <li> + The "Open Source Exception" in the firmware + license means that committing a "binary blob" + driver for the Nvidia Jetson TK1 XHCI device is + acceptable. + </li> </ul> - <p>During this quarter four new commit bits were awarded. Please - welcome Dexuan Cui, David Bright, Konrad Witaszczyk, and Piotr - Stefaniak. We were sorry to see Edwin Lansing hang up his commit - bits and step down from portmgr.</p> + <p>During this quarter four new commit bits were awarded. + Please welcome Dexuan Cui, David Bright, Konrad Witaszczyk, + and Piotr Stefaniak. We were sorry to see Edwin Lansing hang + up his commit bits and step down from portmgr.</p> </body> </project> @@ -813,44 +867,47 @@ </links> <body> - <p>The Ports Tree has reached the marker of 27,000 ports, with the PR count - risen slightly to around 2,250. Of these PRs, 572 are unassigned. The - last quarter saw 6871 commits by 176 committers. The number of open and - the number of unassigned PRs both increased lightly since last quarter.</p> - - <p>Two commit bits were taken in for safe keeping in the last quarter: - jmg after 19 months of inactivity, and edwin at his own request. We - welcomed three new committers: Nikolai Lifanov (lifanov), Jason Bacon, - and Mikhail Pchelin (misha).</p> - - <p>On the management side, adamw and feld were elected as new portmgr - members, and rene was promoted to full member. feld is already involved in - ports-secteam.</p> - - <p>On the infrastructure side, two new USES (lxqt and varnish) were - introduced. Some default versions were also updated: varnish 4 (new), GCC - 4.8 to 4.9, Perl 5.20 to 5.24, and Python 3.4 to 3.5. Two major ports - reached their end-of-life at December 31st and were removed: Perl 5.18 and - Linux Fedora 10 (the default is Linux CentOS 6). Because &os; 9.3, - 10.1, and 10.2 also reached end-of-life, support for those versions was - removed from the Ports Tree.</p> - - <p>Some major ports were updated to their latest versions: pkg to - 1.9.4, Firefox to 50.1.0, Firefox-esr to 45.6.0, Chromium to - 54.0.2840.100, and Ruby to 2.1.10 / 2.2.6 / 2.3.3. - <tt>www/node</tt> was updated to version 7; version 6 was split - off as <tt>www/node6</tt> for long-term support.</p> - - <p>Behind the scenes, antoine ran 39 exp-runs to verify package updates, - framework changes, and changes to the base system. bdrewery installed new - package builders and added builds for &os; 11 for mips, mips64, and - armv6. He also improved the balancing, monitoring, automation of the - package builders.</p> + <p>The Ports Tree has reached the marker of 27,000 ports, with + the PR count risen slightly to around 2,250. Of these PRs, + 572 are unassigned. The last quarter saw 6871 commits by 176 + committers. The number of open and the number of unassigned + PRs both increased lightly since last quarter.</p> + + <p>Two commit bits were taken in for safe keeping in the last + quarter: jmg after 19 months of inactivity, and edwin at his + own request. We welcomed three new committers: Nikolai + Lifanov (lifanov), Jason Bacon, and Mikhail Pchelin + (misha).</p> + + <p>On the management side, adamw and feld were elected as new + portmgr members, and rene was promoted to full member. feld + is already involved in ports-secteam.</p> + + <p>On the infrastructure side, two new USES (lxqt and varnish) + were introduced. Some default versions were also updated: + varnish 4 (new), GCC 4.8 to 4.9, Perl 5.20 to 5.24, and Python + 3.4 to 3.5. Two major ports reached their end-of-life at + December 31st and were removed: Perl 5.18 and Linux Fedora 10 + (the default is Linux CentOS 6). Because &os; 9.3, 10.1, and + 10.2 also reached end-of-life, support for those versions was + removed from the Ports Tree.</p> + + <p>Some major ports were updated to their latest versions: pkg + to 1.9.4, Firefox to 50.1.0, Firefox-esr to 45.6.0, Chromium + to 54.0.2840.100, and Ruby to 2.1.10 / 2.2.6 / 2.3.3. + <tt>www/node</tt> was updated to version 7; version 6 was + split off as <tt>www/node6</tt> for long-term support.</p> + + <p>Behind the scenes, antoine ran 39 exp-runs to verify package + updates, framework changes, and changes to the base system. + bdrewery installed new package builders and added builds for + &os; 11 for mips, mips64, and armv6. He also improved the + balancing, monitoring, automation of the package builders.</p> </body> <help> - <task>If you have some spare time, please take up a PR for testing and - committing.</task> + <task>If you have some spare time, please take up a PR for + testing and committing.</task> </help> </project> @@ -876,16 +933,16 @@ <p>The Minnowboard is an Atom-based x86 board (Intel E38xx Series SoC) in a maker-friendly form-factor: it provides convenient access to pins that can be used to connect - peripherals using one of the standard buses: GPIO, SPI, or I2C. - These buses are more common in the ARM/MIPS world than in x86, - so while &os; was able to boot just fine, it lacked support for - these buses on the MinnowBoard.</p> + peripherals using one of the standard buses: GPIO, SPI, or + I2C. These buses are more common in the ARM/MIPS world than in + x86, so while &os; was able to boot just fine, it lacked + support for these buses on the MinnowBoard.</p> <p>As of r310645, HEAD support all three buses via <tt>ig4(4)</tt>, <tt>bytgpio(4)</tt>, and <tt>intelspi</tt> drivers. The <tt>ig4(4)</tt> and <tt>bytgpio(4)</tt> changes - were backported to 11-STABLE; <tt>intelspi</tt> will be MFCed in - couple of weeks.</p> + were backported to 11-STABLE; <tt>intelspi</tt> will be MFCed + in couple of weeks.</p> </body> </project> @@ -914,24 +971,28 @@ scalability:</p> <ul> - <li><p>Object Storage</p> + <li> + <p>Object Storage</p> <p>Ceph provides seamless access to objects using native language bindings or radosgw, a REST interface that's compatible with applications written for S3 and - Swift.</p></li> - - <li><p>Block Storage</p> + Swift.</p> + </li> + <li> + <p>Block Storage</p> <p>Ceph's RADOS Block Device (RBD) provides access to block device images that are striped and replicated across the - entire storage cluster.</p></li> - - <li><p>File System</p> + entire storage cluster.</p> + </li> + <li> + <p>File System</p> <p>Ceph provides a POSIX-compliant network file system that aims for high performance, large data storage, and maximum - compatibility with legacy applications.</p></li> + compatibility with legacy applications.</p> + </li> </ul> <p>I started looking into Ceph because the HAST solution with @@ -941,40 +1002,48 @@ <tt>bhyve</tt> on RBD disks that are stored in Ceph.</p> <p>The &os; build will build most of the tools in Ceph. Note - that the RBD dependant items will not work, since &os; does not - have RBD (yet).</p> + that the RBD dependant items will not work, since &os; does + not have RBD (yet).</p> <p>Most notable progress since the last report:</p> <ul> - <li>RBD is actually buildable and can be used to manage - <tt>RADOS BLOCK DEVICE</tt>s.</li> - - <li>All tests run to completion for the current selection of + <li> + RBD is actually buildable and can be used to manage + <tt>RADOS BLOCK DEVICE</tt>s. + </li> + <li> + All tests run to completion for the current selection of tools, though the neded (minor) patches have yet to be - pulled into HEAD.</li> - - <li>Cmake is now the only way of building Ceph.</li> - - <li>The threading/polling code has been reworked for the - simple socket code. It now uses a self-pipe, instead of using - an odd <tt>shutdown()</tt>-signaling Linux feature.</li> - - <li>The EventKqueue code was modified to work around the - "feature" that starting threads destroys the kqueue - handles. The code was just finshed, so it is not yet - submitted to the main repository.</li> - - <li>We investigated differences between &os; and Linux for - <tt>SO_REUSEADDR</tt> and <tt>SO_REUSEPORT</tt>. Fortunately, - the code is only used during testing, so disabling these - features only delays progress in the tests.</li> - - <li>A jenkins instances is regularly testing both + pulled into HEAD. + </li> + <li> + Cmake is now the only way of building Ceph. + </li> + <li> + The threading/polling code has been reworked for the simple + socket code. It now uses a self-pipe, instead of using an + odd <tt>shutdown()</tt>-signaling Linux feature. + </li> + <li> + The EventKqueue code was modified to work around the + "feature" that starting threads destroys the + kqueue handles. The code was just finshed, so it is not yet + submitted to the main repository. + </li> + <li> + We investigated differences between &os; and Linux for + <tt>SO_REUSEADDR</tt> and <tt>SO_REUSEPORT</tt>. + Fortunately, the code is only used during testing, so + disabling these features only delays progress in the tests. + </li> + <li> + A jenkins instances is regularly testing both <tt>ceph/ceph/master</tt> and <tt>wjwithagen/ceph/wip.FreeBSD</tt>, so there is regular - verification of buildability and the tests: <a - href="http://cephdev.digiware.nl:8180/jenkins/">http://cephdev.digiware.nl:8180/jenkins/</a>.</li>; + verification of buildability and the tests: + <a href="http://cephdev.digiware.nl:8180/jenkins/">http://cephdev.digiware.nl:8180/jenkins/</a>. + </li> </ul> @@ -992,16 +1061,22 @@ <p>The following setup will get things running for &os;:</p> <ol> - <li>Install bash and link it in <tt>/bin</tt></li> - - <li>It is no longer necessary to add a definition of - <tt>ENODATA</tt> to <tt>/usr/include/errno.h</tt></li> - - <li>Clone the github repo + <li> + Install bash and link it in <tt>/bin</tt> + </li> + + <li> + It is no longer necessary to add a definition of + <tt>ENODATA</tt> to <tt>/usr/include/errno.h</tt> + </li> + <li> + Clone the github repo (http://github.com/wjwithagen/ceph.git) and checkout the - "wip.FreeBSD" branch</li> - - <li>Run <tt>./do_FreeBSD.sh</tt> to start the build.</li> + "wip.FreeBSD" branch + </li> + <li> + Run <tt>./do_FreeBSD.sh</tt> to start the build. + </li> </ol> <p>The old build method using automake is no longer used; see @@ -1010,22 +1085,27 @@ <p>Parts not (yet) included:</p> <ul> - <li>KRBD: Kernel Rados Block Devices is implemented in the - Linux kernel, but not in the &os; kernel. Perhaps - <tt>ggated</tt> could be used as a template since it does some - of the same things as KRBD, just between 2 disks. It also has - a userspace counterpart, which could ease development.</li> - - <li>BlueStore: &os; and Linux have different AIO APIs, and + <li> + KRBD: Kernel Rados Block Devices is implemented in the Linux + kernel, but not in the &os; kernel. Perhaps <tt>ggated</tt> + could be used as a template since it does some of the same + things as KRBD, just between 2 disks. It also has a + userspace counterpart, which could ease development. + </li> + <li> + BlueStore: &os; and Linux have different AIO APIs, and that incompatibility needs to be resolved somehow. Additionally, there is discussion in &os; about - <tt>aio_cancel</tt> not working for all devicetypes.</li> - - <li>CephFS: Cython tries to access an internal field in - <tt>struct dirent</tt>, which does not compile.</li> - - <li>Tests that verify the correct working of the above are - also excluded from the testset.</li> + <tt>aio_cancel</tt> not working for all devicetypes. + </li> + <li> + CephFS: Cython tries to access an internal field in + <tt>struct dirent</tt>, which does not compile. + </li> + <li> + Tests that verify the correct working of the above are + also excluded from the testset. + </li> </ul> </body> @@ -1040,14 +1120,14 @@ developed akin to &os;'s <tt>ggate</tt>.</task> <task>Investigate the keystore, which could be embedded in the - kernel on Linux, and currently prevents building Cephfs and some - other components. The first question whether it is really - required, or if only KRBD require it.</task> + kernel on Linux, and currently prevents building Cephfs and + some other components. The first question whether it is + really required, or if only KRBD require it.</task> <task>Scheduler information is not used at the moment, because the schedulers work rather differently between &os; and Linux. - But a a certain point in time, this would need some attention in - <tt>src/common/Thread.cc</tt>.</task> + But a a certain point in time, this would need some attention + in <tt>src/common/Thread.cc</tt>.</task> <task>Integrate the &os; <tt>/etc/rc.d</tt> initscripts in the Ceph stack. This helps with testing, but also enables running @@ -1128,23 +1208,24 @@ <body> <p>Good progress on graphics support was made during the weeks - around Christmas and the new year with the import of Linux's 4.9 - DRM for <tt>i915</tt> and <tt>amdgpu</tt> into the drm-next - branch of the github repository. The <tt>amdgpu</tt> KMS - driver is already somewhat usable, with a few major known issues - remaining. It now supports GPUs as far back as Southern Islands - and up to Polaris. The 4.9 update also appears to have fixed a - regression in <tt>i915</tt> that was introduced by the 4.8 merge - late this past summer. The drm-next branch now supports the - Intel integrated graphics unit up to Kaby Lake CPUs. To - facilitate out-of-the-box support on CURRENT, most of the - branch-local VM changes were reverted and the graphics fault - routines converted to use pg_populate. This new interface is the - source of a couple of regressions causing panics on i915 and - severe artifacts with amdgpu on integrated GPUs. Mark Johnston - (markj@) has volunteered to analyze these issues. Please show - your support and encouragement to Mark for helping to move this - project towards the finish line.</p> + around Christmas and the new year with the import of Linux's + 4.9 DRM for <tt>i915</tt> and <tt>amdgpu</tt> into the + drm-next branch of the github repository. The <tt>amdgpu</tt> + KMS driver is already somewhat usable, with a few major known + issues remaining. It now supports GPUs as far back as + Southern Islands and up to Polaris. The 4.9 update also + appears to have fixed a regression in <tt>i915</tt> that was + introduced by the 4.8 merge late this past summer. The + drm-next branch now supports the Intel integrated graphics + unit up to Kaby Lake CPUs. To facilitate out-of-the-box + support on CURRENT, most of the branch-local VM changes were + reverted and the graphics fault routines converted to use + pg_populate. This new interface is the source of a couple of + regressions causing panics on i915 and severe artifacts with + amdgpu on integrated GPUs. Mark Johnston (markj@) has + volunteered to analyze these issues. Please show your support + and encouragement to Mark for helping to move this project + towards the finish line.</p> <p>The xserver-mesa-next-udev branch was created for the ports development repository, and holds Mesa 13.0 and fixes for @@ -1157,8 +1238,8 @@ However, the Linux <tt>i915</tt> developers seems to aggressively explore the space of possible implementations and *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201701202212.v0KMCMJ0069365>